Uploaded March 2026 | Updated September 2026, 2 weeks ago
Steve Yegge has spent decades writing software and thinking about how the craft evolves. From his early years at Amazon and Google, to his influential blog posts, he has often been early at spotting shifts in how software gets built.
In this episode of Pragmatic Engineer, I talk with Steve about how AI is changing engineering work, why he believes coding by hand may gradually disappear, and what developers should focus on, instead. We discuss his latest book, Vibe Coding, and the open-source AI agent orchestrator he built called Gas Town, which he said most devs should avoid using.
Steve shares his framework for levels of AI adoption by engineers, ranging from avoiding AI tools entirely, to running multiple agents in parallel. We discuss why he believes the knowledge that engineers need to know keeps changing, and why understanding how systems evolve may matter more than mastering any particular tool.
We also explore broader implications. Steve argues that AI’s role is not primarily to replace engineers, but to amplify them. At the same time, he warns that the pace of change will create new kinds of technical debt, new productivity pressures, and fresh challenges for how teams operate.
—
*Brought to you by our season partners:*
• Statsig — The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic
• Sonar – The makers of SonarQube, the industry standard for automated code review. https://www.sonarsource.com/pragmatic/?utm_medium=paid&utm_source=pragmaticengineer&ut[…]egory=Paid&s_source=Paid%20Other&s_origin=pragmaticengineer
• WorkOS – Everything you need to make your app enterprise ready. workos.com
—
*The Pragmatic Engineer deepdives relevant for this episode:*
• Steve Yegge on AI agents and the future of software engineering newsletter.pragmaticengineer.com/p/steve-yegge-on-ai-agents-and-the
• Vibe coding as a software engineer newsletter.pragmaticengineer.com/p/vibe-coding-as-a-software-engineer
• The full circle of developer productivity with Steve Yegge newsletter.pragmaticengineer.com/p/steve-yegge
• AI Tooling for Software Engineers in 2026 newsletter.pragmaticengineer.com/p/ai-tooling-2026
• The AI Engineering Stack newsletter.pragmaticengineer.com/p/the-ai-engineering-stack
—
*Where to find Steve Yegge:*
• X: https://x.com/steve_yegge
• LinkedIn: linkedin.com/in/steveyegge
• Website: steve-yegge.blogspot.com
• Vibe Coding: itrevolution.com/product/vibe-coding-book
—
*In this episode, we cover:*
(00:00) Intro
(01:43) Steve’s latest projects
(02:27) Important blog posts
(04:48) Shifts in what engineers need to know
(10:46) Steve’s current AI stance
(13:23) Steve’s book Vibe Coding
(18:25) Layoffs and disruption in tech
(31:13) Gas Town
(40:10) New ways of working
(51:08) The problem of too many people
(54:45) Why AI results lag in business
(59:57) Gamification and product stickiness
(1:04:54) The ‘Bitter Lesson’ explained
(1:07:14) The future of software development
(1:23:06) Where languages stand
(1:24:47) Adapting to change
(1:27:32) Steve’s predictions
—
See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast
—
Production and marketing by penname.co/.
Steve Yegge has spent decades writing software and thinking about how the craft evolves. From his early years at Amazon and Google, to his influential blog posts, he has often been early at spotting shifts in how software gets built.
In this episode of Pragmatic Engineer, I talk with Steve about how AI is changing engineering work, why he believes coding by hand may gradually disappear, and what developers should focus on, instead. We discuss his latest book, Vibe Coding, and the open-source AI agent orchestrator he built called Gas Town, which he said most devs should avoid using.
Steve shares his framework for levels of AI adoption by engineers, ranging from avoiding AI tools entirely, to running multiple agents in parallel. We discuss why he believes the knowledge that engineers need to know keeps changing, and why understanding how systems evolve may matter more than mastering any particular tool.
We also explore broader implications. Steve argues that AI’s role is not primarily to replace engineers, but to amplify them. At the same time, he warns that the pace of change will create new kinds of technical debt, new productivity pressures, and fresh challenges for how teams operate.
—
*Brought to you by our season partners:*
• Statsig — The unified platform for flags, analytics, experiments, and more. statsig.com/pragmatic
• Sonar – The makers of SonarQube, the industry standard for automated code review. https://www.sonarsource.com/pragmatic/?utm_medium=paid&utm_source=pragmaticengineer&ut[…]egory=Paid&s_source=Paid%20Other&s_origin=pragmaticengineer
• WorkOS – Everything you need to make your app enterprise ready. workos.com
—
*The Pragmatic Engineer deepdives relevant for this episode:*
• Steve Yegge on AI agents and the future of software engineering newsletter.pragmaticengineer.com/p/steve-yegge-on-ai-agents-and-the
• Vibe coding as a software engineer newsletter.pragmaticengineer.com/p/vibe-coding-as-a-software-engineer
• The full circle of developer productivity with Steve Yegge newsletter.pragmaticengineer.com/p/steve-yegge
• AI Tooling for Software Engineers in 2026 newsletter.pragmaticengineer.com/p/ai-tooling-2026
• The AI Engineering Stack newsletter.pragmaticengineer.com/p/the-ai-engineering-stack
—
*Where to find Steve Yegge:*
• X: https://x.com/steve_yegge
• LinkedIn: linkedin.com/in/steveyegge
• Website: steve-yegge.blogspot.com
• Vibe Coding: itrevolution.com/product/vibe-coding-book
—
*In this episode, we cover:*
(00:00) Intro
(01:43) Steve’s latest projects
(02:27) Important blog posts
(04:48) Shifts in what engineers need to know
(10:46) Steve’s current AI stance
(13:23) Steve’s book Vibe Coding
(18:25) Layoffs and disruption in tech
(31:13) Gas Town
(40:10) New ways of working
(51:08) The problem of too many people
(54:45) Why AI results lag in business
(59:57) Gamification and product stickiness
(1:04:54) The ‘Bitter Lesson’ explained
(1:07:14) The future of software development
(1:23:06) Where languages stand
(1:24:47) Adapting to change
(1:27:32) Steve’s predictions
—
See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast
—
Production and marketing by penname.co/.
