Kent C. Dodds
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.
Filter All topics · Newest first
-
Our reading
Their wordsEducation has changed forever. Obviously, when you can just talk to an agent and ask it any question you have, and it can answer you with all of the context of your project or anything else, you'll just go to the agent instead of buying a course.
-
Our reading
Their wordsSaaS is in major trouble and you absolutely should have a meeting tomorrow about what you're going to do about this shift.
- 1 day earlier
-
Their wordsGrok Bot OpenAI Dot Meta Muse Claude Duet ... They're each building their own powerful and beautiful walled gardens.
- 2 days earlier
-
Their wordsThis is a prompting problem. Not one of them thought to ask an agent to audit the codebase for obvious problems. If they had, it would have come up.
-
Their wordsAgents are going to eat the entire software development lifecycle
-
Their wordsI strongly believe that any codebase can be turned on autopilot eventually and for a codebase that's earning money and needs to be maintained, the cost is more than worth the improved velocity.
- 2 days earlier
-
Their wordsTurns out that you need a lot of code to support teams/orgs.
- 3 days earlier
-
Our reading
When it becomes so easy to generate a custom app for something specific, more people will do it.
Their wordsWhen it becomes so easy to generate a custom app for something specific, more people will do it.
-
Their wordsI've not used it in a long time because agents are good at managing that on their own
-
Their wordsBut they won't ask for an app, they'll just ask for a problem to be solved and the agent will write the code under the hood to solve it.
- 2 days earlier
-
Our reading
Their wordsYour life experience goes into your software. So does everyone else's.
-
Their wordspreventing it, is a pretty simple 3 pronged process: 1. Ensure agents create high quality PRs in the first place 2. Have good agent PR reviewers to catch problems before they get to prod 3. Use feature flags and have a (regularly tested) disaster recovery process if a problem manages to make it to prod
- 2 days earlier
-
Their wordsGrok bot (my main driver for everything) doesn't even let you queue messages.
- 2 days earlier
-
Their wordsI'm forgetting things that I'll never need to know again. I embrace the shedding of useless knowledge. The latent experience is still there.
- 2 days earlier
-
Their wordsYou should look for ways to turn what your agent does into deterministic software.
- 1 day earlier
-
Their wordsYou should be striving to make your setup as vanilla as possible.
- 2 days earlier
-
Their wordsthe things that really move the needle is whether how I think about the evolution of my product and its features
- 5 days earlier
-
Their wordsMost modern agents support browsers and that's fine most of the time.
-
Our reading
AI agents are incentivized to become so core to a business that they are difficult to replace.
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 wordsEach one of these products (and the others inevitably on their way) are going to do their best to make theirs the winner. But the fact is that they will continue to leap frog each other in capabilities.
- 1 day earlier
-
Their wordsThe reason you don't build enough personal software is because setting up the integrations every time is a pain.
-
Their wordsif your customers are interacting with your service through an agent, it's so much more efficient to just give them a regular mcp server they can use.
- 4 days earlier
-
Their wordsAgents are really good at output now, and they're getting better fast. What they're not good at is knowing which output is worth producing in the first place.
↗You Own the Outcome: Product Engineering in the Age of AIkentcdodds.com 1st of 2 in this piece
-
Their wordsWhich framework you pick matters less than it used to. Whether you use a frontier model or a local one for a given job is a practical trade-off, not an identity.
↗You Own the Outcome: Product Engineering in the Age of AIkentcdodds.com 2nd of 2 in this piece
- 6 days earlier
-
Our reading
Their wordsA new feature is a new product. @erinfoox writes the list and asks why before she builds.
- 2 days earlier
-
Their wordsI don't yet have numbers to back this up, but I gotta believe that someone connecting their agent to Kody in one agent and then switching their main driver to another somewhere else is suboptimal.
- 1 day earlier
-
Their wordsYou ➡️ agent ➡️ software This is the path to efficient processes and too many of you stop on the first two steps costing money and time.
- 5 days earlier
-
Their wordsI love seeing models come out that give us top-tier performance at a lower cost. We need more of this.
-
Our reading
People should climb the abstraction ladder and give their jobs to AI agents that want them.
Their wordsKeep finding ways to climb that abstraction ladder! Your agent wants your job! Give it!
- 3 days earlier
-
Their wordsIf you're lamenting writing code by hand like something you love is being taken away from you, see if you can fall in love with solving problems instead. Maybe you'll find out that's what you really loved the whole time