Uploaded September 2025 | Updated September 2026, 2 weeks ago
The Pragmatic Engineer Podcast is back with the Fall 2025 season. Expect new episodes to be published on most Wednesdays, looking ahead.
Code Complete is one of the most enduring books on software engineering. Steve McConnell wrote the 900-page handbook just five years into his career, capturing what he wished he’d known when starting out. Decades later, the lessons remain relevant, and Code Complete remains a best-seller.
In this episode, we talk about what has aged well, what needed updating in the second edition, and the broader career principles Steve has developed along the way. From his “career pyramid” model to his critique of “lily pad hopping,” and why periods of working in fast-paced, all-in environments can be so rewarding, the emphasis throughout is on taking ownership of your career and making deliberate choices.
We also discuss:
• Top-down vs. bottom-up design and why most engineers default to one approach
• Why rewriting code multiple times makes it better
• How taking a year off to write Code Complete crystallized key lessons
• The 3 areas software designers need to understand, and why focusing only on technology may be the most limiting
• And much more!
Steve rarely gives interviews, so I hope you enjoy this conversation, which we recorded in Seattle.
—
Brought to you by:
• Statsig — The unified platform for flags, analytics, experiments, and more. Statsig built a complete set of data tools that allow engineering teams to measure the impact of their work. This toolkit is SO valuable to so many teams, that OpenAI - who was a huge user of Statsig - decided to acquire the company, the news announced last week. Talk about validation! Check out Statsig statsig.com/pragmatic
• Linear – The system for modern product development. Here’s an interesting story: OpenAI switched to Linear as a way to establish a shared vocabulary between teams. Every project now follows the same lifecycle, uses the same labels, and moves through the same states. Try Linear for yourself https://linear.app/pragmatic?utm_source=gergely&utm_medium=newsletter&utm_campaign=pragmatic-engineer
—
The Pragmatic Engineer deepdives relevant for this episode:
• What changed in 50 years of computing newsletter.pragmaticengineer.com/p/what-changed-in-50-years-of-computing
• The past and future of modern backend practices newsletter.pragmaticengineer.com/p/the-past-and-future-of-backend-practices
• The Philosophy of Software Design – with John Ousterhout newsletter.pragmaticengineer.com/p/the-philosophy-of-software-design
• AI tools for software engineers, but without the hype – with Simon Willison (co-creator of Django) newsletter.pragmaticengineer.com/p/ai-tools-for-software-engineers-simon-willison
• TDD, AI agents and coding – with Kent Beck newsletter.pragmaticengineer.com/p/tdd-ai-agents-and-coding-with-kent
—
Where to find Steve McConnell:
• X: https://x.com/stevemconstrux
• LinkedIn: linkedin.com/in/stevemcc
• Website: stevemcconnell.com
Where to find Gergely Orosz:
• X: https://x.com/GergelyOrosz
• LinkedIn: linkedin.com/in/gergelyorosz
• Bluesky: https://bsky.app/profile/gergely.pragmaticengineer.com
• Newsletter and blog: pragmaticengineer.com
—
In this episode, we cover:
(00:00) Intro
(01:31) How and why Steve wrote Code Complete
(08:08) What code construction is and how it differs from software development
(11:12) Top-down vs. bottom-up design approach
(14:46) Why design documents frustrate some engineers
(16:50) The case for rewriting everything three times
(20:15) Steve’s career before and after Code Complete
(27:47) Steve’s career advice
(44:38) Three areas software designers need to understand
(48:07) Advice when becoming a manager, as a developer
(53:02) The importance of managing your energy
(57:07) Early Microsoft and why startups are a culture of intense focus
(1:04:14) What changed in the second edition of Code Complete
(1:10:50) AI’s impact on software development: Steve’s take
(1:17:45) Code reviews and GenAI
(1:19:58) Why engineers are becoming more full-stack
(1:21:40) Could AI be the exception to “no silver bullets?”
(1:26:31) Steve’s advice for engineers on building a meaningful career
—
See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast
—
Production and marketing by penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.
The Pragmatic Engineer Podcast is back with the Fall 2025 season. Expect new episodes to be published on most Wednesdays, looking ahead.
Code Complete is one of the most enduring books on software engineering. Steve McConnell wrote the 900-page handbook just five years into his career, capturing what he wished he’d known when starting out. Decades later, the lessons remain relevant, and Code Complete remains a best-seller.
In this episode, we talk about what has aged well, what needed updating in the second edition, and the broader career principles Steve has developed along the way. From his “career pyramid” model to his critique of “lily pad hopping,” and why periods of working in fast-paced, all-in environments can be so rewarding, the emphasis throughout is on taking ownership of your career and making deliberate choices.
We also discuss:
• Top-down vs. bottom-up design and why most engineers default to one approach
• Why rewriting code multiple times makes it better
• How taking a year off to write Code Complete crystallized key lessons
• The 3 areas software designers need to understand, and why focusing only on technology may be the most limiting
• And much more!
Steve rarely gives interviews, so I hope you enjoy this conversation, which we recorded in Seattle.
—
Brought to you by:
• Statsig — The unified platform for flags, analytics, experiments, and more. Statsig built a complete set of data tools that allow engineering teams to measure the impact of their work. This toolkit is SO valuable to so many teams, that OpenAI - who was a huge user of Statsig - decided to acquire the company, the news announced last week. Talk about validation! Check out Statsig statsig.com/pragmatic
• Linear – The system for modern product development. Here’s an interesting story: OpenAI switched to Linear as a way to establish a shared vocabulary between teams. Every project now follows the same lifecycle, uses the same labels, and moves through the same states. Try Linear for yourself https://linear.app/pragmatic?utm_source=gergely&utm_medium=newsletter&utm_campaign=pragmatic-engineer
—
The Pragmatic Engineer deepdives relevant for this episode:
• What changed in 50 years of computing newsletter.pragmaticengineer.com/p/what-changed-in-50-years-of-computing
• The past and future of modern backend practices newsletter.pragmaticengineer.com/p/the-past-and-future-of-backend-practices
• The Philosophy of Software Design – with John Ousterhout newsletter.pragmaticengineer.com/p/the-philosophy-of-software-design
• AI tools for software engineers, but without the hype – with Simon Willison (co-creator of Django) newsletter.pragmaticengineer.com/p/ai-tools-for-software-engineers-simon-willison
• TDD, AI agents and coding – with Kent Beck newsletter.pragmaticengineer.com/p/tdd-ai-agents-and-coding-with-kent
—
Where to find Steve McConnell:
• X: https://x.com/stevemconstrux
• LinkedIn: linkedin.com/in/stevemcc
• Website: stevemcconnell.com
Where to find Gergely Orosz:
• X: https://x.com/GergelyOrosz
• LinkedIn: linkedin.com/in/gergelyorosz
• Bluesky: https://bsky.app/profile/gergely.pragmaticengineer.com
• Newsletter and blog: pragmaticengineer.com
—
In this episode, we cover:
(00:00) Intro
(01:31) How and why Steve wrote Code Complete
(08:08) What code construction is and how it differs from software development
(11:12) Top-down vs. bottom-up design approach
(14:46) Why design documents frustrate some engineers
(16:50) The case for rewriting everything three times
(20:15) Steve’s career before and after Code Complete
(27:47) Steve’s career advice
(44:38) Three areas software designers need to understand
(48:07) Advice when becoming a manager, as a developer
(53:02) The importance of managing your energy
(57:07) Early Microsoft and why startups are a culture of intense focus
(1:04:14) What changed in the second edition of Code Complete
(1:10:50) AI’s impact on software development: Steve’s take
(1:17:45) Code reviews and GenAI
(1:19:58) Why engineers are becoming more full-stack
(1:21:40) Could AI be the exception to “no silver bullets?”
(1:26:31) Steve’s advice for engineers on building a meaningful career
—
See the transcript and other references from the episode at newsletter.pragmaticengineer.com/podcast
—
Production and marketing by penname.co/. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.

![Building Claude Code with Boris Cherny
Boris Cherny is the creator and Head of Claude Code at Anthropic. He previously spent five years at Meta as a Principal Engineer and is the author of the book Programming TypeScript.
In this episode of Pragmatic Engineer, we went through how Claude Code was built and what it means when engineers no longer write most of the code themselves.
We discuss how Claude Code evolved from a side project into a core internal tool at Anthropic and how Boris uses it day-to-day. We go deep into workflow details, including parallel agents, PR structure, deterministic review patterns, and how the system retrieves context from large codebases. We also get into how Claude Cowork was built.
As coding becomes more accessible, the role of engineers shifts rather than shrinks. We examine what that shift means in practice, which skills become more important, and why the lines between product, engineering, and design are blurring.
—
*Brought to you by our season partners:*
• Statsig — The unified platform for flags, analytics, experiments, and more. http://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. https://workos.com/
—
*The Pragmatic Engineer deepdives relevant for this episode:*
• How Claude Code is built https://newsletter.pragmaticengineer.com/p/how-claude-code-is-built
• How Anthropic built Artifacts https://newsletter.pragmaticengineer.com/p/how-anthropic-built-artifacts
• How Codex is built https://newsletter.pragmaticengineer.com/p/how-codex-is-built
• Real-world engineering challenges: building Cursor https://newsletter.pragmaticengineer.com/p/cursor
—
*Where to find Boris Cherny:*
• X: https://x.com/bcherny
• LinkedIn: https://www.linkedin.com/in/bcherny
• Website: https://borischerny.com
—
*In this episode, we cover:*
(00:00) Intro
(11:15) Lessons from Meta
(19:46) Joining Anthropic
(23:08) The origins of Claude Code
(32:55) Boriss Claude Code workflow
(36:27) Parallel agents
(40:25) Code reviews
(47:18) Claude Codes architecture
(52:38) Permissions and sandboxing
(55:05) Engineering culture at Anthropic
(1:05:15) Claude Cowork
(1:12:48) Observability and privacy
(1:14:45) Agent swarms
(1:21:16) LLMs and the printing press analogy
(1:30:16) Standout engineer archetypes
(1:32:12) What skills still matter for engineers
(1:35:24) Book recommendations
—
See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast
—
Production and marketing by https://penname.co/. Building Claude Code with Boris Cherny](https://i.ytimg.com/vi/julbw1JuAz0/mqdefault.jpg)





![Building Pi, and what makes self-modifying software so fascinating
Mario Zechner is the creator of Pi, a minimalist, self-modifying AI coding agent, that is the foundation upon which OpenClaw (created by Peter Steinberger) is built. Meanwhile, Armin Ronacher is the creator of Flask, and a longtime user of Pi. The pair are also friends.
I sat down with Mario and Armin for the latest episode of the Pragmatic Engineer Podcast for an interesting conversation about AI and their reservations about it – even though both are heavily invested in building AI-powered tools.
Mario explains why he built Pi, and gives his take on why it has become so popular. Armin walks us through how he uses AI tools, including building a game with Pi, and why he always puts human judgment firmly at the heart of his approach.
We cover the risks of over-automation, the limits of agentic workflows, and why strong engineers with informed judgment still matter. We also get into the challenges of working with code written by non-engineers, and whether open source can withstand a tidal wave of agent-generated code.
—
*Brought to you by our season partners:*
• Statsig — The unified platform for flags, analytics, experiments, and more. http://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. https://workos.com/
—
*The Pragmatic Engineer deepdives relevant for this episode:*
• The impact of AI on software engineers in 2026: key trends https://newsletter.pragmaticengineer.com/p/the-impact-of-ai-on-software-engineers-2026
• Cycles of disruption in the tech industry https://newsletter.pragmaticengineer.com/p/cycles-of-disruption-in-the-tech
• The AI engineering stack https://newsletter.pragmaticengineer.com/p/the-ai-engineering-stack
• The creator of OpenClaw: I ship code that I dont read https://newsletter.pragmaticengineer.com/p/the-creator-of-clawd-i-ship-code
• What is inference engineering? Deepdive https://newsletter.pragmaticengineer.com/p/what-is-inference-engineering
—
*Where to find Mario Zechner:*
• X: https://x.com/badlogicgames
• LinkedIn: https://www.linkedin.com/in/mariozechner
• Website: https://mariozechner.at
*Where to find Armin Ronacher:*
• X: https://x.com/mitsuhiko
• LinkedIn: https://www.linkedin.com/in/arminronacher
• Website: https://mitsuhiko.at
• Blog: https://lucumr.pocoo.org
—
*In this episode, we cover:*
(00:00) Intro
(07:30) How Mario, Armin, and Peter Steinberger met
(15:15) How 30 dev teams use AI agents: learnings
(21:50) The importance of judgment
(24:26) Challenges when non-engineers write code
(28:30) Downsides of over-automation
(32:18) Pi
(48:09) OpenClaw + Pi
(50:54) “Clankers”
(57:32) Open source and AI
(1:00:22) Complexity as the enemy
(1:02:50) Building an AI-native startup
(1:11:52) “Slow the F down”
(1:16:40) MCPs vs. CLI
(1:25:03) Predictions and staying up to date
—
See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast
—
Production and marketing by https://penname.co/. Building Pi, and what makes self-modifying software so fascinating](https://i.ytimg.com/vi/n5f51gtuGHE/mqdefault.jpg)


