Software engineer and educator; creator of Testing Library and of the EpicWeb.dev and EpicReact.dev courses.
Kent C. Dodds did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording.
Their own site.
Is this you? Claim it or ask us to remove it.Or tell us what is wrong here.
Kent C. DoddsSoftware engineer and educatorBut the thing is, they all want to drive their claws so deep into the flesh of your business (to be useful of course), that it will be a huge chore to get rid of them. The integrations, automations, memories, secret tokens, etc etc etc. All of these will be locked into the assistant and they are not incentivized to make it easy for you to transfer these things to your "new hire."↗@kentcdodds on Xx.com · 29 Sept 2026
Their wordsBut the thing is, they all want to drive their claws so deep into the flesh of your business (to be useful of course), that it will be a huge chore to get rid of them. The integrations, automations, memories, secret tokens, etc etc etc. All of these will be locked into the assistant and they are not incentivized to make it easy for you to transfer these things to your "new hire."
Their wordsThat is the part that usually makes architectural iteration slow: you have to build the thing before you can have an informed opinion about whether it is the right thing.