korrents
Kent C. Dodds

Kent C. Dodds

@kent-c-dodds · 42 positions · On ppll ↗

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.

The ideas Kent C. Dodds's claims keep coming back to. The labels are ours; every quote is Kent C. Dodds's own words.

Holds now (6)

How these views changed over time2018–2026
Sort
Show

Each column is a stretch of time in which the same views came up; a new column starts when one appears or goes quiet. Quiet means nothing on it in our sources for that stretch, which is not the same as a change of mind; Dropped means they said they no longer hold it; tap the card for which claim and when. Revised means the view carries on but one of its claims was dropped. Each row is one view, in the same place all the way along. The number is how many claims in that stretch; we hold 3 in 2018, 0 in 2019, 0 in 2020, 0 in 2021, 0 in 2022, 1 in 2023, 2 in 2024, 1 in 2025, 41 in 2026.

Test software the way it is used, not its implementation details

Our label. 3 claims in Kent C. Dodds's own words.

Write tests. Not too many. Mostly integration.

  1. Kent C. Dodds Software engineer and educator "Write tests. Not too many. Mostly integration." - @rauchg Here's my talk from @assertjs two weeks ago dissecting that statement. @kentcdodds on Xx.com · 5 Mar 2018
    "Write tests. Not too many. Mostly integration." - @rauchg Here's my talk from @assertjs two weeks ago dissecting that statement.
  2. Guillermo Rauch CEO of Vercel; creator of Next.js and Socket.IO Write tests. Not too many. Mostly integration. @rauchg on Xx.com · 10 Dec 2016
    Write tests. Not too many. Mostly integration.

Good things happen when you do not test implementation details: tests written with the React and Vue testing libraries look almost identical.

  1. Kent C. Dodds Software engineer and educator Did you know, the tests you write with react-testing-library look almost identical to the tests you write with vue-testing-library. Magic things happen when you don't test implementation details. :) @kentcdodds on Xx.com · 20 Oct 2018
    Did you know, the tests you write with react-testing-library look almost identical to the tests you write with vue-testing-library. Magic things happen when you don't test implementation details. :)

Agents will take over most of the work of writing and maintaining software

Our label. 5 claims in Kent C. Dodds's own words.

Any codebase can be turned on autopilot eventually

  1. Kent C. Dodds Software engineer and educator I 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. @kentcdodds on Xx.com · 20 Oct 2026
    I 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.

People will ask for a problem to be solved and an agent will write the code under the hood to solve it.

  1. Kent C. Dodds Software engineer and educator But 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. @kentcdodds on Xx.com · 15 Oct 2026
    But 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.

Once an agent can do a task, turn it into deterministic software

Our label. 3 claims in Kent C. Dodds's own words.

The path to efficient processes is person to agent to software, and stopping before software costs money and time.

  1. Kent C. Dodds Software engineer and educator You ➡️ agent ➡️ software This is the path to efficient processes and too many of you stop on the first two steps costing money and time. @kentcdodds on Xx.com · 15 Sept 2026
    You ➡️ agent ➡️ software This is the path to efficient processes and too many of you stop on the first two steps costing money and time.

It is more efficient to give customers a regular MCP server if they are interacting with a service through an agent.

  1. Kent C. Dodds Software engineer and educator if 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. @kentcdodds on Xx.com · 28 Sept 2026
    if 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.

Agents make custom and personal software cheap enough that more people will build it

Our label. 3 claims in Kent C. Dodds's own words.

AI coding agents have made redesigning existing systems cheap enough that developers actually redesign instead of living with a flawed design.

  1. Kent C. Dodds Software engineer and educator AI agents make redesigns cheap. The reason I could go through three rounds of "build, ship, regret, redesign" in a matter of days is that the agent did most of the implementation work. Implementing Hybrid Semantic + Lexical Searchkentcdodds.com · 16 Mar 2026All korrents from this piece
    AI agents make redesigns cheap. The reason I could go through three rounds of "build, ship, regret, redesign" in a matter of days is that the agent did most of the implementation work.

Agent platforms are building walled gardens meant to be hard to leave, while none stays ahead for long

Our label. 4 claims in Kent C. Dodds's own words.

AI agents are incentivized to become so core to a business that they are difficult to replace.

Lock-in and switching costs

  1. Kent C. Dodds Software engineer and educator But 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
    But 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."

AI agents will leapfrog each other in capabilities.

  1. Kent C. Dodds Software engineer and educator Each 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. @kentcdodds on Xx.com · 29 Sept 2026
    Each 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.

Connecting an agent to Kody in one agent tool and then switching the main driver to another tool is likely suboptimal, though not yet backed by numbers.

  1. Kent C. Dodds Software engineer and educator I 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. @kentcdodds on Xx.com · 16 Sept 2026
    I 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.

Agents produce output; deciding what is worth building is still the person's job

Our label. 4 claims in Kent C. Dodds's own words.

Agents are good at producing output but not at judging which output is worth producing in the first place.

  1. Kent C. Dodds Software engineer and educator Agents 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 · 24 Sept 2026All korrents from this piece
    Agents 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.

Anyone mourning the loss of writing code by hand should try falling in love with solving problems instead — that may be what they loved the whole time.

  1. Kent C. Dodds Software engineer and educator If 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 @kentcdodds on Xx.com · 7 Sept 2026
    If 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