korrents

What Kent Beck thinks about design

@kent-beck · 38 positions · 0 changes of mind

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.

9 dated positions, 2026, in their own words. Our reading of what Kent Beck has said — not written or endorsed by them.

9 positions so far — this page is not yet offered to search engines.

  1. You look under the underneath though at the code and it was just a horrible unmaintainable mess. But the fact that people could program the programs that they wanted was a a significant step forward as opposed to I'm going to write a thousandpage requirements document and then wait 8 years and not get what I want which was the alternative that we were offering at the at the time.

    How Kent Beck shapes the software engineering industryyoutube.com 4th of 28 in this recording

  2. Your understanding of somebody else's problem is bounded because you're not in the middle of it. You don't have the same skin in the game. If you're not semiconductor test engineer, you don't have as much skin in the game as somebody who is because they're going to have to be using this interface for a long time after you're gone.

    How Kent Beck shapes the software engineering industryyoutube.com 6th of 28 in this recording

    semiconductors

  3. So a a big challenge in object-oriented programming is dividing the responsibilities because you're moving the computation to where the data is. Saying, "Well, this object does this and that object does that is a really critical decision because you want to you want the computation near to the data so that there's less coupling between them." which is a lesson that I I think uh kind of got lost in the noise. That's the fundamental design move in ob in designing object-oriented programs and I I think I stand behind that.

    How Kent Beck shapes the software engineering industryyoutube.com 7th of 28 in this recording

  4. It's not always pleasant. It's not a pat you on the head and you're going to be fine. It's a It's a don't like no, you're screwing this up. Go try this thing. Tell me how that works. Oh, you didn't try the thing. Oh, you don't want to work on this? Okay, we're done. Quite uncompromising. uh I say coaches are are there to identify and induce productive discomfort

    How Kent Beck shapes the software engineering industryyoutube.com 20th of 28 in this recording

  5. So, we're going to see people get into those where they're like, "Well, I vibe code the tip of the iceberg. I throw away the rest of the iceberg and now I'm in trouble because now I don't know what to do. Now I get to these downstream problems that I didn't even know existed." So, we're going to see on the on the side of the the the vibe coding replacers, we're going to see that kind of a naivity play out.

    How Kent Beck shapes the software engineering industryyoutube.com 24th of 28 in this recording

    vibe coding

  6. 3 months earlier
  7. And one of the things I noticed is for 25 years we've kind of had the answers. Somebody comes to us and says we have too many bugs or like, all right, well, here's how you write tests. Oh, I can't write tests. Well, here's how you design so you can write tests. It's just kind of press play uh on the recorder. And the thing that's changed is at this moment nobody knows the answers to anything.

    Martin Fowler & Kent Beck: Frameworks for reinventing software, again and againyoutube.com 1st of 20 in this recording

  8. Yeah, AI is an amplifier. And if uh if you're young and learning quickly, AI is going to amplify that or can amplify that. So, I I personally think this is this is the golden age of the junior programmer.

    Martin Fowler & Kent Beck: Frameworks for reinventing software, again and againyoutube.com 10th of 20 in this recording

    AI and jobs

  9. So, I see a a big trend is the re-soloing of programming. Where a big part of extreme programming is creating a safe social environment for basically antisocial people. Not just asocial, antisocial. And the when I think about the degree of interaction on an XP team, people aren't talking to each other hours a day and happy to be doing so because it's set up for that to be a positive experience.

    Martin Fowler & Kent Beck: Frameworks for reinventing software, again and againyoutube.com 15th of 20 in this recording

  10. But my my experience pairing with a two humans and a genie or multiple genies has been very positive. And the fact that they're kind of slow is really nice. So, every time the models come out and they're faster, I'm like, "Oh, there's less time to talk."

    Martin Fowler & Kent Beck: Frameworks for reinventing software, again and againyoutube.com 18th of 20 in this recording