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
In an interview published by The Pragmatic Engineer, Titus Winters discussed engineering practices he helped develop at Google and his work on computer science curriculum guidelines. He also questioned whether AI-driven increases in code output are improving software delivery, citing conversations with engineers who reported more outages but no rise in features shipped.
Titus Winters, a former Google engineer and lead author of Software Engineering at Google, discussed large-scale code refactoring, mandatory testing and changes to computer science education in an interview published by The Pragmatic Engineer. The conversation also examined whether AI-generated code is improving software outcomes, a question with consequences for engineering teams and new graduates.
Winters spent more than a decade at Google, where he led the company’s readability program and helped develop Abseil, its open-source foundational C++ libraries. He is now a Senior Principal Scientist at Adobe, focusing on developer experience and productivity, according to the report. The interview covered his work on updated ACM/IEEE undergraduate computer science curriculum guidelines as well as software engineering practices used at Google.
One project discussed was a 2010 effort to refactor a large portion of Google’s C++ codebase. Winters recalled a team of about 12 engineers working across a codebase then described as close to 250 million lines, edited by roughly 10,000 engineers. The team used parsing and automated code generation to identify and change patterns, while allowing old and new APIs to coexist during the rollout. The report says the need for tooling during this work helped lead to the clang-format toolkit.
Winters also described Google’s response to a slowdown in Search releases. The report says that around 2007 the product had fallen from a monthly shipping cadence to quarterly releases. Google then required each change to include a test, according to Winters’ account. The interview links that practice, along with code review and the readability program, to making changes safer and supporting ongoing software engineering.
Engineering Practices at Google
The interview connects testing, code review and large-scale refactoring to a practical problem: how organizations can change complex software without making every update a high-risk event. Winters’ account suggests that engineering safeguards are not only about catching defects; they can also give teams more confidence to modify code and maintain release work.
That issue is timely as teams adopt AI coding tools. Winters said that engineers he speaks with at other companies report substantially more code output than a year earlier, but also about 30% more outages and no increase in features shipped. This is an attributed observation from his conversations, not a measured industry-wide study in the supplied report. Still, it highlights why code volume alone may not show whether AI is making software teams more productive.
For students and early-career engineers, the discussion also raises a question about what a computer science degree should prepare them to do. The report says Winters is involved in curriculum guideline work and discusses changes he believes are needed, but the supplied material does not detail a finalized curriculum or specific adopted requirements.
Products Worth Considering
Bose SoundLink Flex (2nd Gen) Portable Bluetooth Speaker
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
Sonos Era 100 SL Compact, Microphone-Free Speaker – Black
As an affiliate, we earn on qualifying purchases.
From Code Cleanup to Curriculum
Winters joined Google in 2010, according to the report, and took part in a refactoring project addressing old C++ patterns across a very large codebase. The work predated today’s large language models. The team parsed build targets into abstract syntax trees, matched specific call patterns and generated edits, then rolled changes out in batches. The old API was removed after the new one had been adopted.
Google’s readability process, as described in the interview, required review by both a project or file owner and a language readability reviewer. The report says that when Winters left Google three months before its publication, more than 10,000 engineers were enrolled in the program at a given time. The source does not provide an independently verified count or specify the exact date of his departure.
The conversation ranges from these company practices to undergraduate education. The report frames the tension as a question of whether traditional computer science teaching still matches software work today. Winters helped author the book Software Engineering at Google and has worked on ACM/IEEE curriculum guidelines, but the supplied excerpt does not include the full interview or its detailed proposals.
“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 C++ refactoring project
Limits of the AI Productivity Claims
The reported 30% rise in outages comes from Winters’ conversations with engineers at other companies. The source does not name those companies, define the period or measurement method, or establish a comparison group. It should not be treated as a representative industry statistic or proof that AI coding tools caused outages.
The supplied report excerpt ends partway through its discussion of AI, so it does not provide the full account of potential benefits or Winters’ complete reasoning. It also does not specify what changes he proposes for computer science education, whether curriculum guidelines have been adopted, or when any revisions would take effect. Those details remain unclear from the material provided.
Curriculum and AI Questions Ahead
The interview is available through The Pragmatic Engineer and its listed podcast platforms. The next concrete developments to watch are whether the ACM/IEEE curriculum work leads to published, specific guidance and how educators respond to any proposed revisions. The supplied material gives no release schedule or decision date for those guidelines.
For claims about AI and engineering outcomes, more detail would be needed to establish whether reported changes in code output and outages hold across organizations and time periods. Until comparable data are available, Winters’ figures remain an account of what he has heard from engineers, rather than a confirmed sector-wide trend.
Key Questions
Who is Titus Winters?
Winters spent more than a decade at Google, where he led its readability program and helped develop 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 refactoring project involve?
A team of about 12 engineers used language parsing and automated edits to update old C++ patterns across a codebase described in the report as close to 250 million lines. The work was carried out while the codebase remained in use.
Did Google require tests for every change?
Winters said Google mandated that each change be accompanied by a test after Search could no longer release at its previous cadence. This is his account of the company’s response, as reported by The Pragmatic Engineer.
Does the interview prove AI is causing more outages?
No. Winters said engineers he speaks with report about 30% more outages alongside higher code output and no rise in features shipped. The report does not provide a study design or evidence establishing that AI caused those outages.
What changes to computer science education are proposed?
The interview discusses Winters’ work on ACM/IEEE undergraduate curriculum guidelines and his view that traditional education needs revision. The supplied source material does not list specific recommendations or say whether any have been formally adopted.
Source: newsletter.pragmaticengineer.com
