@Pragmatic_Eng: Anyone who thinks software engineering is ‘going away’ doesn’t understand the job. @KentBeck, creator of XP and TDD, on…

X AI KOLs Following News

Summary

Kent Beck argues that software engineering is not going away even as AI advances, because coding involves building trust, understanding, and connections that cannot be automated.

Anyone who thinks software engineering is ‘going away’ doesn’t understand the job. @KentBeck, creator of XP and TDD, on why Dario has it wrong: [Gergely: Dario said, I quote, ‘coding is going away first, then all of software engineering’. ] “That's a statement by someone who doesn't understand software engineering. Coding is part of what you're doing, but it's only a small part of what you're doing, even if it takes up a fair amount of time. You're building confidence, you're building connections with other people, you’re building your own understanding. All those things are happening while you're coding. And coding's actually a great way to cement understanding. The more you program, the more you understand the domain that you're working in. And so to say, well, we're just going to pass all that off to a machine. Well, that's not all there is to it. A couple of days ago I saw a phrase, and it really hit me, that we're accumulating code faster than we're accumulating trust now. And that sense of trust comes from me struggling to understand some domain concept, ah, I get it! I represented it in the code. I write tests that demonstrate that I really did understand it and now, I trust my program. If we're programming together, that act of programming together means that we trust each other more. And none of that can be automated. None of that occurs. If we prompt, we get the finger guns, the genie goes, yeah, it's all finished, boss. And it is like, well, hang on, finished. What's finished?”
Original Article
View Cached Full Text

Cached at: 07/03/26, 04:32 AM

Anyone who thinks software engineering is ‘going away’ doesn’t understand the job. @KentBeck, creator of XP and TDD, on why Dario has it wrong:

[Gergely: Dario said, I quote, ‘coding is going away first, then all of software engineering’. ]

“That’s a statement by someone who doesn’t understand software engineering. Coding is part of what you’re doing, but it’s only a small part of what you’re doing, even if it takes up a fair amount of time.

You’re building confidence, you’re building connections with other people, you’re building your own understanding. All those things are happening while you’re coding. And coding’s actually a great way to cement understanding. The more you program, the more you understand the domain that you’re working in. And so to say, well, we’re just going to pass all that off to a machine. Well, that’s not all there is to it.

A couple of days ago I saw a phrase, and it really hit me, that we’re accumulating code faster than we’re accumulating trust now. And that sense of trust comes from me struggling to understand some domain concept, ah, I get it! I represented it in the code. I write tests that demonstrate that I really did understand it and now, I trust my program. If we’re programming together, that act of programming together means that we trust each other more.

And none of that can be automated. None of that occurs. If we prompt, we get the finger guns, the genie goes, yeah, it’s all finished, boss. And it is like, well, hang on, finished. What’s finished?”

Similar Articles

@saranormous: https://x.com/saranormous/status/2064510215056400652

X AI KOLs Following

Despite rapid advances in AI coding agents like Devin, which have dramatically increased code writing and shipping, the article argues that the most valuable aspects of software engineering remain illegible to benchmarks and require human judgement and organizational coordination that cannot be easily automated.

Why AI hasn’t replaced software engineers, and won’t

Simon Willison's Blog

Arvind Narayanan and Sayash Kapoor argue that AI will not replace software engineers, citing bottlenecks like deciding what to build, verification, and deep human understanding as key to the profession's resilience against automation.