The third golden age of software engineering – thanks to AI, with Grady Booch
February 4, 2026
AI Summary
5 min read🎙️ The Voices & The Context
- The Format: Interview-style podcast with deep historical dive into software engineering.
- The Key Players:
- Guest: Grady Booch – Pioneering software engineer, co-creator of UML, IBM Fellow, witness to industry shifts since the 1970s; famous for object-oriented design and demystifying AI's impact.
- Host: Tech podcaster (Pragmatic Engineer vibe), probing with questions on history, AI fears, and future skills.
- The Vibe: Educational and optimistic – a masterclass blending history lessons with reassurance amid AI hype, countering existential dread with excitement.
🗝️ Key Themes & Topics
Grady frames software engineering's history as three golden ages driven by rising abstractions, paralleling today's AI shift.
- Topic 1: Origins & First Golden Age (1940s-1970s): Margaret Hamilton coins "software engineering"; focus on algorithmic abstractions for business/math (e.g., Fortran), amid "software crisis" of complexity and scale. Fringe innovations in defense (SAGE, Whirlwind) push real-time/distributed systems.
- Topic 2: Second Golden Age (1980s-2000s): Object-oriented abstractions (Simula, C++) tackle complexity; rise of PCs, open source, platforms (e.g., SaaS precursors), internet embedding software in society. Y2K as invisible success story.
- **Topic 3: Third Golden Age (2000s-N
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
What you'll learn
- 1 (00:00) **🎙️ Introduction: Grady Booch**
- 2 (01:09) **Origins of Software Engineering**
- 3 (05:23) **First Golden Age: Late 1940s–Late 1970s**
- 4 (18:06) **Software Crisis and Transition**
- 5 (26:14) **Second Golden Age: 1980s–2000s**
- 6 (41:25) **AI History Parallels Software Ages**
- 7 (48:51) **Third Golden Age: Systems, Security, Ethics**
+ Full timestamped outline available in the app
Show Notes
Brought to You By:
• Statsig — The unified platform for flags, analytics, experiments, and more.
• Sonar – The makers of SonarQube, the industry standard for automated code review
• WorkOS – Everything you need to make your app enterprise ready.
—
Every few decades, software engineering is declared “dead” or on the verge of being automated away. We’ve heard versions of this story before. But what if it’s just the start of a new “golden age” of a different type of software engineering, like it has been many times before?
In this episode of The Pragmatic Engineer, I’m joined once again by Grady Booch, one of the most influential figures in the history of software engineering, to put today’s claims about AI and automation into historical context.
Grady is the co-creator of the Unified Modeling Language, author of several books and papers that have shaped modern software development, and Chief Scientist for Software Engineering at IBM, where he focuses on embodied cognition.
Grady shares his perspective on three golden ages of computing since the 1940s, and how each emerged in response to the constraints of its time. He explains how technical limits and human factors have always shaped the systems we build, and why periods of rapid change tend to produce both real progress and inflated expectations.
He also responds to current claims that software engineering will soon be fully automated, explaining why systems thinking, human judgment, and responsibility remain central to the work, even as tools continue to evolve.
—
Timestamps
(00:00) Intro
(01:04) The first golden age of software engineering
(18:05) The software crisis
(32:07) The second golden age of software engineering
(41:27) Y2K and the Dotcom crash
(44:53) Early AI
(46:40) The third golden age of software engineering
(50:54) Why software engineers will very much be needed
(57:52) Grady responds to Dario Amodei
(1:06:00) New skills engineers will need to succeed
(1:09:10) Resources for studying complex systems
(1:13:39) How to thrive during periods of change
—
The Pragmatic Engineer deepdives relevant for this episode:
More from this podcast
The Pragmatic Engineer →