Navigating Growth in Tech Companies

This chapter examines the transition of startups into large corporations, focusing on the experiences of technology companies like Google and IBM. It highlights the significance of employee demographics and personal stories from Microsoft, emphasizing the balance of technical skills and business knowledge for software developers. The discussion also addresses challenges faced by technical managers and the dynamics of small, motivated teams in fostering innovation within the tech industry.

Transcript

chevron_right

Play full episode

chevron_right

Transcript

Episode 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