What Kent Beck thinks about software quality
Creator of extreme programming and test-driven development, an original signatory of the Agile Manifesto, and the author of Test-Driven Development: By Example and Tidy First?
Kent Beck 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.
6 dated positions, 2026, in their own words. Our reading of what Kent Beck has said — not written or endorsed by them.
-
Their wordswe're accumulating code faster than we're accumulating trust and that sense of trust comes from me struggling to understand some domain concept I get it. I represent it in the code. I have I write tests that demonstrate that I really did understand it. And now I trust my program.
↗How Kent Beck shapes the software engineering industryyoutube.com 2nd of 28 in this recording
-
Their wordsSo beforehand because of this social divide between programmers and testers. There was a lot of incentive for the testers to have their own language. This is my tool. I know how to run it. I'm going to run it.
↗How Kent Beck shapes the software engineering industryyoutube.com 8th of 28 in this recording
-
Their wordsIt costs tokens in the short run, but it can save them in the long run because one of the classic genie mistakes is stuff doesn't work.
↗How Kent Beck shapes the software engineering industryyoutube.com 11th of 28 in this recording
-
Their wordsAnd then there were people who used it as a moral cudgel. Like you should be if you're not using TDD, you're not professional. And that's just such People can write very good software with a wide variety of workflows.
↗How Kent Beck shapes the software engineering industryyoutube.com 12th of 28 in this recording
-
Their wordsIt's when you have this rapid alternation between I do a thing, I learn a thing, I do a thing, I learn a thing, I do a thing, I learn a thing. That's where TDD is really powerful. But it's not a moral decision. It's a practical decision.
↗How Kent Beck shapes the software engineering industryyoutube.com 13th of 28 in this recording
-
Their wordsThen you had code review which gave you another level of feedback. You could roll out internally more frequently. And everybody was using Facebook for all kinds of stuff, personal and internal business stuff. So whatever feature you developed, people would start using it immediately. So you get another round of feedback. Then we had this phased roll out process where you'd start rolling your stuff out. If there was a problem, the blast radius would be limited to a a few million people.
↗How Kent Beck shapes the software engineering industryyoutube.com 18th of 28 in this recording