AI Summary
5 min readIn 1987, Kent Beck sat next to Ward Cunningham at Tektronix and watched him code. Beck was a 24-year-old punk with attitude, and Cunningham was a master programmer. For a while, Beck wasn't allowed to touch the keyboard. He just watched, absorbing low-level patterns, and eventually started making suggestions. Over months, they developed a style where the keyboard went back and forth, and they talked at multiple levels simultaneously — about why code wasn't working, what tools would make it easy, what the design should be, and whether they should be doing it at all. This rhythm of intense collaboration, weekly coffee meetings, and rapid prototyping produced a string of tech reports and tools, including Hot Draw, a graphics editor whose name came from the sheer excitement of seeing smooth animation on screen for the first time. That partnership with Ward Cunningham set the pattern for Beck's entire career: try the stupid idea, throw it away if it doesn't work, and build the playbook as you go.
The human side of software engineering
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of The Pragmatic Engineer
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (02:06) **Dario's "Coding is going away" claim** - Kent responds to the viral tweet, arguing it misunderstands what software engineering actually involves
- 2 (06:35) **Early life and first contact with computers** - Growing up in Silicon Valley before it was Silicon Valley, with a father who was an electrical engineer
- 3 (12:10) **College years and the music detour** - University of Oregon, switching between computer science and music, and the long path to a master's degree
- 4 (15:38) **First job at Tektronics and meeting Ward Cunningham** - Joining the Smalltalk team, the beauty of the language, and the beginning of a legendary collaboration
- 5 (25:28) **Pair programming with Ward Cunningham and the birth of design patterns** - How they developed a programming style, Hot Draw, and the influence of Christopher Alexander
- 6 (42:22) **Apple years and getting fired** - Joining Apple's Smalltalk project, then Alan Kay's Playground project, and the consequences of being a "punk"
- 7 (49:27) **CRC cards and the origin of SUnit** - Ward Cunningham's idea for visualizing object-oriented design, and Kent's synthesis of a unit testing framework
+ Full timestamped outline available in the app
Show Notes
Brought to You By:
• Antithesis – verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.
• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable.
• WorkOS – everything you need to make your app enterprise ready.
—
Few have made as big an impact on software engineering as this week’s guest on the Pragmatic Engineer podcast, Kent Beck. He created Extreme Programming, pioneered test-driven development (TDD), co-created JUnit, and is one of the authors of the famous ‘Agile Manifesto’. But these days, he's re-examining many ideas for the age of AI, and says we’re failing to accumulate trust during this new era at the same high rate as new code is being accumulated.
In this episode of the Pragmatic Engineer podcast, Kent and I dig into his journey from discovering Smalltalk in the early days of personal computing, to helping define modern software engineering practices. We explore the origins of TDD, design patterns, Extreme Programming, and Agile – along with some lessons learned at Apple and Facebook.
Kent explains why he believes software engineering is about far more than writing code, why no one yet knows exactly how engineers should work alongside AI agents, and how his "explore, expand, extract" framework can help engineers navigate major technology shifts.
—
Timestamps
00:00 Intro
03:47 Human engineers aren’t going away
08:00 Kent's path into tech
13:50 Undergraduate and graduate studies
17:21 Kent’s first programming job
18:54 The rise and fall of Smalltalk
27:04 Working with Ward Cunningham
37:36 Design patterns
44:05 Working at Apple
51:08 CRC Cards
59:29 Testing tools in the language
1:04:22 The C3 project with Martin Fowler
1:09:54 Extreme Programming
1:16:25 Developing TDD
1:25:07 Writing the Agile Manifesto
1:30:00 Agile’s impact
1:32:40 Agile’s downside
1:37:32 The Dotcom Bust
1:44:30 Lessons from working at Facebook
1:59:44 Kent’s ‘Good to Great’ program at Facebook
2:06:07 Soft skills engineers need to learn
2:09:30 AI and the challenges of acceleration
2:15:53 Explore, expand, extract
2:22:33 What Kent is excited about
—
The Pragmatic Engineer deepdives relevant for this episode:
• Measuring developer productivity? A response to McKinsey – co-w
More from this podcast
The Pragmatic Engineer →