TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The Pragmatic Engineer published an interview 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. Winters also discusses AI’s effects on software work, but the available source presents his observations rather than independently verified industry-wide data.
The Pragmatic Engineer has published an interview with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, about the company’s large-scale C++ refactoring, engineering practices and changes he believes are needed in computer science education. The conversation also addresses AI’s effects on developer productivity, a topic Winters discusses partly through observations from conversations with engineers at other companies.
Winters spent more than a decade at Google, where he led the company’s readability program and helped build Abseil, Google’s open-source C++ libraries. The source says he is now a senior principal scientist at Adobe, focused on developer experience and productivity. The podcast interview covers his work on the ACM/IEEE undergraduate computer science curriculum guidelines, though the excerpt does not give specific proposed curriculum changes.
A central example is a refactoring effort begun at Google in 2010. According to the report, the company then had close to 250 million lines of code, maintained by about 10,000 engineers. A team of roughly a dozen people worked to replace an old C++ API across the codebase. They used language parsing, abstract syntax trees and generated edits to identify and update code, rather than changing each instance by hand. The team also made the old and new APIs coexist during the rollout.
The discussion also revisits Google’s approach to testing and review. The report says Google required changes to be accompanied by tests after Search struggled to maintain a monthly release cadence around 2007. It describes code review as involving both a project or file owner and a language-specific readability reviewer. By the time Winters left Google, the source says, more than 10,000 engineers were enrolled in the readability program at a given time.
Engineering Practices Behind Safer Changes
The interview connects testing, code review and large-scale refactoring to a practical question for software teams: how can engineers change systems without making them less reliable? The Google examples suggest that automated checks and structured review can support changes across a large, shared codebase, where a local edit may affect many teams or products.
That theme also informs Winters’ views on education. The source frames the interview around his work revising undergraduate computer science guidance and his argument that much of the existing curriculum needs major change. Readers should distinguish that characterization from a detailed curriculum proposal: the supplied excerpt does not lay out which courses or requirements he would replace, or what the revised guidance says.
The AI discussion adds a current workplace concern, but should be read as Winters’ reported assessment, not a measured industry finding. The report attributes to him an estimate that outages at companies he speaks with are up about 30% while feature output remains static, alongside a large increase in code output. The excerpt provides no sample, measurement method or comparison period for those figures.
Products Worth Considering
Logitech MX Keys S Wireless Keyboard, Graphite
Bose TV Speaker (2nd Gen) Compact Soundbar with Bluetooth and HDMI
Anker SOLIX S2000 Portable Power Station, 2,010Wh, 1,500W
As an affiliate, we earn on qualifying purchases.
From Google Refactoring to Curriculum Work
The C++ refactor took place before today’s generative AI tools. The report says the team used parsing and code-generation methods to identify exact patterns, generate changes, distribute edits in batches and prevent the old pattern from returning. The work also led to the creation of the clang-format toolkit, according to the source. These details illustrate how teams can automate repetitive changes while retaining control over their rollout.
Google’s testing and readability practices developed in response to the scale and interdependence of its software. The report says changes across the organization often affected Search, contributing to pressure on release schedules. Testing requirements and specialist review were presented as organizational responses; the excerpt does not provide independent records or quantify their effects beyond saying Search later returned to a higher release cadence.
Winters’ education work is connected to the ACM and IEEE undergraduate curriculum guidelines. The source identifies him as a lead author of Software Engineering at Google and says he worked on updating those guidelines. It does not specify the publication or adoption status of any revised curriculum document.
“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 C++ refactoring project
Details Missing From the Interview Excerpt
The provided source is an excerpt and promotional summary, not a full transcript. It does not establish the episode’s exact publication date, provide the complete discussion of AI, or specify Winters’ recommended changes to computer science courses. The report’s characterization that he wants to “burn down” almost all of the existing curriculum is a framing of his position; the excerpt does not include enough detail to assess the scope of that proposal.
The reported 30% rise in outages is also not backed in the excerpt by a named dataset, defined time window, company sample or baseline. It should not be treated as a verified industry-wide statistic. The source does not identify which companies were included or explain how code output, outages and features shipped were measured.
Full Episode and Curriculum Proposals
The source directs readers to watch or listen to the full episode on YouTube, Apple and Spotify, and says a transcript and timestamps are available on the episode page. Those materials are needed to check the full context of Winters’ remarks, particularly his specific proposals for computer science education and the evidence behind his AI-related observations.
The excerpt does not announce a release date or decision point for updated ACM/IEEE curriculum guidance. Until further details are available, the next developments to watch are publication of the full interview and any formal curriculum recommendations that identify proposed changes, their rationale and how they may be adopted by universities.
Key Questions
What is the news?
The Pragmatic Engineer published a podcast interview with Titus Winters about software engineering at Google, computer science education and AI’s effects on development work.
Who is Titus Winters?
Winters spent more than a decade at Google, where he led its readability program and helped build the Abseil C++ libraries. The source 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?
The report describes a project begun in 2010 to replace an old API across a codebase of close to 250 million lines. A small team used parsing, abstract syntax trees and generated edits to update code in stages while the old and new APIs coexisted.
Did Winters say AI is increasing software outages?
The report attributes to Winters an estimate of about 30% more outages among companies he speaks with, alongside increased code output and static feature counts. The excerpt does not provide a dataset, sample, measurement method or time window, so this is not established as an industry-wide result.
What changes does Winters propose for computer science education?
The source says Winters worked on updating ACM/IEEE undergraduate computer science curriculum guidelines and frames him as calling for major changes. The excerpt does not identify specific courses, requirements or a finalized proposal.
Source: newsletter.pragmaticengineer.com
