Software engineering at Google & CS education with Titus Winters
October 29, 2026
AI Summary
5 min readTitus Winters, the only active software engineer on the steering committee that defines the undergraduate computer science curriculum, argues that most of it should be burned down. Winters spent over a decade at Google, co-authored Software Engineering at Google, and ran the company's readability program. In this conversation, he explains why Google made testing mandatory around 2006, how to think about developer productivity in the age of AI, and what he would change about CS education.
Why Google Made Tests Mandatory
The origin of Google's famously rigorous testing culture was not academic idealism—it was a crisis. Around 2006, the flagship search product could no longer ship on a regular cadence. The team was aiming for monthly releases but could only manage one per quarter because of persistent regressions. The architecture was so tightly coupled that changes to Gmail could break search. The release engineers drew a line: no code would be merged without tests. Period. No VP could override it. As Winters puts it, "fear is not an acceptable basis for engineering." A codebase is sustainable, he argues, only if you can safely make any valuable change that comes along. If you are afraid to change something, you have to fix that first.
The Largest Refactoring in Human History
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 (00:05) **The Problem with CS Education** - Titus Winters, the only active software engineer on the ACM/IEEE CS curriculum steering committee, argues most of the curriculum should be "burned down."
- 2 (00:34) **Google’s Test Mandate Origin** - Why Google made tests mandatory around 2006: the flagship search product could no longer release on a regular cadence due to persistent regressions.
- 3 (00:39) **Measuring Developer Productivity** - Why the value of AI does not show up in the metrics we measure today.
- 4 (00:48) **How Titus Would Change CS Education** - Including grading students on their prompts and tests, not the code itself.
- 5 (02:50) **Titus’s Path to Tech and Google** - Self-taught via QBasic, a PhD in CS Education, and a difficult Google interview where he skipped the hotel.
- 6 (08:35) **Joining Google and the “Nuclear Hat”** - His initial team was a poor fit; he moved to a team maintaining old C++ infrastructure code.
- 7 (13:26) **Why Google’s Test Culture Enabled Refactoring** - The fear-free environment from the 2006 test mandate allowed him to safely change core libraries.
+ Full timestamped outline available in the app
Show Notes
Brought to You By:
• turbopuffer – a vector and full-text search engine built on object storage. It’s fast, cheap, and extremely scalable
• Linear – the product development system for teams and agents
• WorkOS – everything you need to make your app enterprise ready.
—
An engineer who helped create today’s software engineering curriculum now says to burn down almost all of it. What’s the cause of this contradiction? We find out from the lead author of Software Engineering at Google.
Titus Winters spent more than a decade at Google, where he led its readability program and built Abseil, Google’s open-sourced foundational C++ libraries. He is currently a Senior Principal Scientist at Adobe, where he focuses on developer experience and productivity.
In this episode of The Pragmatic Engineer podcast, Titus and I discuss how his team tackled a massive refactoring project across Google's 250-million-line C++ codebase, why Google made testing mandatory, and his work on updating the ACM/IEEE undergraduate computer science curriculum guidelines.
We also explore why traditional productivity metrics miss some of AI’s biggest benefits, what needs to change in CS education, and how new engineers can stand out.
Timestamps
00:00 Intro
07:01 Getting hired by Google
09:48 Finding his niche at Google
14:32 Why Google made testing mandatory
17:45 Why new engineers fear making mistakes
20:40 Abseil: C++ foundations at Google
23:09 Google’s massive C++ refactoring
30:48 AI for rewrites
39:07 Software Engineering at Google: the book
43:10 Google’s readability reviews
47:18 Why teams still matter
52:41 Psychological safety
58:17 Layoffs and culture
1:02:11 Measuring developer productivity
1:11:17 Rethinking CS education
1:22:56 What new grads should learn
1:32:08 Titus’s ideal software engineering curriculum
1:36:27 Advice for breaking into tech
1:38:35 Book recommendation
—
The Pragmatic Engineer deepdives relevant for this episode:
• The state of the tech industry in 2026
• Inside Google's Engineering Culture
•
More from this podcast
The Pragmatic Engineer →