TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The Pragmatic Engineer published a podcast conversation with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, about large-scale refactoring, testing, code review and computer science education. The discussion also raises questions about AI’s effect on software productivity; the source gives Winters’ observations, not independently verified industry-wide data.
The Pragmatic Engineer has published a podcast interview with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, on the company’s large-scale engineering practices and the future of computer science education. The conversation covers a 250-million-line C++ refactoring effort, testing and code review at Google, and Winters’ work on updating undergraduate curriculum guidelines.
Winters spent more than a decade at Google, where he led the company’s readability program and helped build Abseil, its open-source foundational C++ libraries. The report says he is now a Senior Principal Scientist at Adobe, focusing on developer experience and productivity. The podcast was hosted by The Pragmatic Engineer’s editor, who presented the discussion as a look at how large engineering organizations maintain and change software.
One episode topic is a refactor begun in 2010, when Google had close to 250 million lines of code edited by about 10,000 engineers, according to the report. A team of roughly a dozen used language-parsing techniques to identify targeted code patterns, generate edits and replace an old API while allowing the old and new versions to coexist. The work also prompted development of the clang-format toolkit, the report says.
The conversation also revisits Google’s response to a slowdown in Search releases. Winters said that around 2007 the product could no longer ship monthly and was releasing about quarterly. The company then required changes to be accompanied by tests, according to the report. The discussion describes a separate review model in which changes require approval from a project owner and a language-specific readability reviewer. The report says more than 10,000 engineers were enrolled in the readability program when Winters left Google.
Engineering Practices Under Scrutiny
The interview connects day-to-day engineering rules to the ability to maintain large software systems. Automated tests and structured review can help teams identify problems before changes reach production, while large refactors show how code can be altered systematically rather than by relying on manual edits alone. These are practices Winters describes from Google; the interview does not establish that every organization can apply them in the same way.
The discussion is also relevant to developers and educators because it links software practice with computer science curriculum guidance. Winters worked on updating ACM/IEEE undergraduate curriculum guidelines, and the episode asks what new engineers need to learn as development tools change. The source describes his criticism of traditional education, but does not provide the full revised curriculum or a final set of recommendations.
On AI, Winters offers a caution against treating higher code output as proof of greater productivity. The report attributes to him an observation that engineers he speaks with are seeing code output rise while outages are also up by about 30% and feature delivery remains static. That figure is not accompanied in the supplied material by a defined sample, measurement period or comparison baseline, so it should be read as his reported observation—not as a verified industry-wide statistic.
Products Worth Considering
Bose QuietComfort Wireless Bluetooth Headphones with Active Noise Cancellation, Mic, USB‑C Charging, Deep Bass, 24‑Hour Battery – White Smok
Samsung 27-inch Odyssey OLED G6 QD-OLED QHD Gaming Monitor
Bose SoundLink Flex (2nd Gen) Portable Bluetooth Speaker
As an affiliate, we earn on qualifying purchases.
From Google Refactoring to Curriculum
The episode draws on Winters’ experience with several efforts inside Google: a codebase-wide C++ migration, mandatory testing and an organized reviewer education program. The report presents these not as one new company announcement but as examples from a career spent improving how engineers work across a large organization.
Winters also co-authored Software Engineering at Google and contributed to work on undergraduate computer science curriculum guidelines. The tension highlighted by the podcast is that someone involved in shaping software engineering education now argues that much of the existing curriculum needs major change. The supplied excerpt introduces that argument but does not fully specify which parts of the curriculum Winters would retain or replace.
“We were replacing the foundation of the Empire State Building. We were not allowed to close the building or block traffic. Oh, and we discovered nuclear waste in the basement.”
— Titus Winters, recalling Google’s large C++ refactoring effort
AI Metrics Need More Detail
The supplied report is an account of a podcast conversation, not a formal study of Google’s engineering outcomes or a representative survey of software companies. It does not provide the underlying data behind Winters’ roughly 30% outage increase observation, including the companies covered, the time period, or how outages were counted. The comparison cannot be independently assessed from the excerpt.
The source material also cuts off during its discussion of AI, after introducing a possible counterpoint to the reported outages. It therefore does not include Winters’ complete account of AI’s benefits, his full recommendations for CS education, or the episode’s complete treatment of productivity measures. No specific curriculum changes or adoption timeline are set out in the supplied text.
Curriculum Recommendations Ahead
The immediate next step for readers seeking Winters’ complete arguments is the full podcast and transcript referenced by The Pragmatic Engineer. The supplied report says the episode is available on YouTube, Apple and Spotify, but it does not state a publication date or identify a further announcement tied to the discussion.
For the education debate, the relevant development to follow is how the ACM/IEEE undergraduate curriculum guidance is revised and what changes Winters supports. For the AI discussion, more detailed, clearly defined data would be needed to establish whether the reported relationship among code output, outages and feature delivery holds beyond the engineers he has spoken with.
Key Questions
Who is Titus Winters?
Winters spent more than a decade at Google, where he led its readability program and helped build Abseil. The report identifies him as a Senior Principal Scientist at Adobe and a lead author of Software Engineering at Google.
What did the Google C++ refactoring involve?
According to The Pragmatic Engineer, a team of about a dozen engineers worked on changes across a codebase of close to 250 million lines in 2010. They used parsing and code-generation techniques to find and replace specific patterns while keeping old and new APIs usable during the migration.
What does Winters say about AI and software productivity?
The report attributes to Winters an observation from conversations with engineers: code output has risen, outages are up about 30%, and feature delivery is static. The excerpt does not specify the sample, period or comparison baseline, so the figure is not confirmed as an industry-wide measure.
What is Winters’ position on computer science education?
The episode discusses Winters’ work updating ACM/IEEE undergraduate curriculum guidelines and his argument that much of the existing curriculum needs major change. The supplied source excerpt does not give a complete list of the changes he proposes.
Source: newsletter.pragmaticengineer.com
