Code Complete with Steve McConnell

Key takeaways

Writing a detailed plan can lead to unexpected outcomes in projects.
Understanding code construction is crucial for producing high-quality software.
Different engineers may favor different design approaches, impacting project outcomes.
A clear career development model can provide direction and prevent aimlessness in career moves.
AI tools can enhance coding but require careful consideration to ensure accuracy and reliability.
Fast-paced environments can foster rapid skill development but need energy management to sustain effectiveness.

Summary

Writing Code Complete

Steve McConnell discusses how he originally set out to write a shorter article but ended up with the monumental task of creating 'Code Complete.' He emphasizes the importance of having a clear target audience in mind during the writing process and shares his surprising journey in estimating the book's page count.

The Concept of Code Construction

McConnell differentiates between coding and software construction, explaining how his book addresses the often-overlooked aspects of producing quality software. He stresses the relevance of code construction and the iterative mindset required to enhance the software build processes.

Top-down vs. Bottom-up Design

The episode dives into design methodologies where McConnell highlights the contrast between top-down and bottom-up approaches in software design. He provides insights into how different engineers tend to favor one method over the other.

Career Development Insights

McConnell shares his career model, which he terms the 'career pyramid.' This framework helps individuals visualize their career paths, stressing the need for a balanced skill set and avoiding 'lily pad hopping' where professionals change jobs without accumulating meaningful experience.

The Impact of AI on Software Development

The conversation shifts to AI's growing role in software engineering, exploring how tools like generative AI can help developers but also introducing challenges of ensuring the correctness of automatically generated code. McConnell emphasizes the enduring need for human oversight in software engineering.

Lessons from Fast-Paced Work Environments

Fast-paced work environments, akin to startups, can lead to rewarding experiences, allowing software engineers to develop their skills rapidly. McConnell reflects on the chaotic yet fulfilling nature of such environments and the importance of energy management in a career.

Show notes

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.

•⁠ 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.

—

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.

—

Timestamps

(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

—

The Pragmatic Engineer deepdives relevant for this episode:

• What changed in 50 years of computing

• The past and future of modern backend practices

• The Philosophy of Software Design – with John Ousterhout

• AI tools for software engineers, but without the hype – with Simon Willison (co-creator of Django)

• TDD, AI agents and coding – with Kent Beck

—

Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email podcast@pragmaticengineer.com.

Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe