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 interview with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, about large-scale code refactoring, testing, code review and computer science education. The interview also discusses AI’s effects on software productivity, but the source offers Winters’ observations rather than 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, examining how Google handled large-scale software changes and how computer science education may need to adapt. The discussion also covers AI’s effects on engineering work, including Winters’ account of rising outages at companies he speaks with, a claim the supplied report does not independently substantiate.
Winters spent more than a decade at Google, where he led the company’s readability program and helped build Abseil, Google’s open-source foundational C++ libraries. He is now a senior principal scientist at Adobe, working on developer experience and productivity, according to The Pragmatic Engineer. The podcast revisits his work on the book Software Engineering at Google and his involvement in updating undergraduate computer science curriculum guidance developed by the ACM and IEEE.
A central example is a Google C++ refactoring effort from 2010. Winters recalled that the company then had close to 250 million lines of code, edited by about 10,000 engineers. A team of roughly a dozen people worked on replacing old code patterns across the codebase. The account describes parsing build targets into abstract syntax trees, matching specific call patterns, generating edits, and distributing changes in batches. The team also developed tools and procedures to prevent old patterns from returning; the report says the work led to the creation of the clang-format toolkit.
The interview also traces Google’s testing and review practices. Winters said Google made tests mandatory for changes after Search struggled to maintain a monthly release cadence, and described a review system requiring approval from both 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 three months before the source was written; the report does not specify the date of that departure.
Why Google’s Review Practices Matter
The examples in the interview concern a practical problem for large software organizations: how to change widely used code without making systems harder to maintain or disrupting releases. Automated tests, structured reviews and tools for mechanical code changes can create safeguards that let teams update software with fewer risks. Winters’ account presents these practices as organizational choices, not simply technical tools.
The AI discussion matters because faster code production does not necessarily mean more useful software is reaching users. Winters said that, based on conversations with engineers at other companies, code output had risen substantially compared with a year earlier while outages had also increased by about 30% and feature releases remained static. That is his reported observation, not a measured, independently verified industry statistic; the source gives no sample, measurement method or exact comparison window. It nonetheless points to a question for engineering leaders: whether productivity measures capture reliability and maintenance as well as the volume of code produced.
His comments on computer science education also speak to students and employers facing changes in software development. The discussion raises the possibility that curriculum guidelines should put more weight on the practices needed to work safely in existing systems, rather than treating programming as code production alone. The supplied report does not set out a final curriculum proposal.
Products Worth Considering
Bose QuietComfort Wireless Bluetooth Headphones with Active Noise Cancellation, Mic, USB‑C Charging, Deep Bass, 24‑Hour Battery – White Smok
LG UltraGear 32GX850A-B 32-Inch 4K UHD Glossy OLED Gaming Monitor
Bose TV Speaker (2nd Gen) Compact Soundbar with Bluetooth and HDMI
As an affiliate, we earn on qualifying purchases.
From Google’s Codebase to CS Curricula
The Pragmatic Engineer frames the conversation around an apparent tension: Winters helped shape software engineering education through his book and curriculum work, yet argues in the interview that much of the existing curriculum needs major revision. The report’s introductory description says he calls for burning down almost all of it, but the supplied material does not include the full discussion or a detailed list of what should replace current courses. That characterization should be read as the publication’s summary of the conversation, not as a complete curriculum plan.
Google’s refactoring example illustrates the scale of the engineering environment behind the interview. In 2010, the team could not simply pause work across a codebase maintained by thousands of engineers. Instead, it used parsing and generated edits to make changes in stages, while allowing old and new interfaces to coexist during the work. The process predated large language models, according to the report, and relied on language tooling and controlled rollout rather than AI-generated edits.
The company’s review model paired domain knowledge from a project owner with language-specific guidance from a certified reviewer. The source describes the program as a large-scale educational effort inside Google, with new engineers also receiving guidance on their first code changes. These details provide context for Winters’ broader focus on developer experience, safe changes and how engineers learn.
“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 the Google refactoring project, as quoted by The Pragmatic Engineer
Limits of the AI Outage Claim
The source does not identify the companies behind Winters’ reported 30% increase in outages, how many engineering teams he consulted, or how outages and code output were measured. It also does not state the precise period used for the comparison beyond saying output was much higher than a year earlier. The figure should not be treated as a verified industry-wide trend.
The supplied report is an episode summary, not a full transcript. It introduces a discussion of AI’s potential benefits but cuts off before providing those details. It therefore does not establish the overall effect of AI on software productivity or explain how Winters weighs benefits against outages.
It is also unclear what specific changes Winters recommends for undergraduate computer science programs. The report identifies his work on ACM/IEEE curriculum guidance and summarizes his criticism of existing education, but it does not provide the proposed revisions, their status, or whether the professional bodies have adopted any changes.
Full Interview and Curriculum Details
The podcast episode is available on YouTube, Apple and Spotify, according to The Pragmatic Engineer, with a transcript and episode timestamps linked from the publication. Listening to the full conversation would provide more detail on Winters’ views about AI, the curriculum work and what he believes new engineers need to learn.
No upcoming curriculum decision, implementation date or formal ACM/IEEE action is identified in the supplied material. Further developments would need to clarify whether the interview’s criticism leads to specific proposed guidelines, and how educators might respond. For the AI claims, additional evidence would be needed to establish whether the reported outage pattern applies beyond the engineers Winters described.
Key Questions
Who is Titus Winters?
Winters spent more than a decade at Google, where he led its readability program and helped build Abseil, according to The Pragmatic Engineer. He is now a senior principal scientist at Adobe focused on developer experience and productivity.
What did the Google C++ refactoring involve?
The report describes a 2010 effort to update patterns across a codebase then estimated at nearly 250 million lines. A small team used code parsing, pattern matching and generated edits to carry out changes in stages while the code remained in use.
Did AI cause outages to rise by 30%?
That is not established by the supplied source. Winters reported hearing from engineers at other companies that outages were up about 30%, alongside increased code output and static feature releases. The report provides no sample or measurement method, so the figure is an attributed observation, not verified industry data.
What changes to computer science education does Winters propose?
The source says Winters argues that much of the existing curriculum needs major revision and notes his work on ACM/IEEE undergraduate curriculum guidance. It does not provide a detailed list of proposed changes or say that any revisions have been adopted.
Source: newsletter.pragmaticengineer.com
![Rails World 2026 Opening Keynote [Video]](https://1023jack.com/wp-content/uploads/2026/09/rails-world-2026-opening-keynote-video-featured-560x300.jpg)
