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. The discussion covers large-scale refactoring, testing and code review at Google, AI’s effects on engineering work, and Winters’ role in updating undergraduate computer science curriculum guidance.
The Pragmatic Engineer has published a podcast interview with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, covering large-scale code changes, testing, AI and computer science education. The conversation matters to engineers and educators because Winters discusses how practices built for maintaining complex software may inform both industry work and undergraduate curricula.
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. He is now a senior principal scientist at Adobe, focusing on developer experience and productivity, according to the podcast’s introduction. The interview also covers his work on updating the ACM/IEEE undergraduate computer science curriculum guidelines.
One account concerns a 2010 effort to refactor a large C++ codebase. Winters recalled that Google then had close to 250 million lines of code, maintained by about 10,000 engineers. A team of roughly a dozen worked on replacing an old API across the codebase. The source describes a process using parsing and abstract syntax trees, pattern matching, generated edits and staged rollout—not language models, which were not available for the project at the time.
The conversation also revisits Google’s decision to require tests with changes after its Search product struggled to ship more frequently than quarterly around 2007, a discussion relevant to how software engineering careers may evolve. The source says nearly every change at Google could affect Search, and that the organization-wide testing requirement was followed by a return to a faster release cadence. Winters also discusses code review: the source describes a process requiring approval from a project owner and a language-specific readability reviewer.
Engineering Practices at Scale
The examples in the interview show why testing, review and safe refactoring are more than local coding preferences: at a large organization, they can shape how quickly teams can make changes without destabilizing existing systems. The account of Google’s C++ migration illustrates the work involved in changing shared foundations while keeping software in use.
For readers in computer science education, the curriculum discussion connects those operational lessons to what students are taught. The interview’s framing suggests that engineering education should account for the realities of maintaining and changing software, not only writing new programs. That is a topic of debate rather than a confirmed description of a finalized curriculum revision.
Winters also raises a question about how to measure AI’s effect on software development. The source reports his observation that some engineers he speaks with describe much higher code output alongside more outages and no corresponding increase in features shipped. That is an attributed impression, not independently established industry-wide data, but it highlights why output volume alone may not capture whether AI tools improve engineering outcomes.
Products Worth Considering
Anker SOLIX S2000 Portable Power Station, 2,010Wh, 1,500W
Bose QuietComfort True Wireless Earbuds with Active Noise Cancellation, Black
Samsung 27-inch Odyssey OLED G6 QD-OLED QHD Gaming Monitor
As an affiliate, we earn on qualifying purchases.
From Google Refactoring to Curriculum
The Pragmatic Engineer presents the episode as a conversation about lessons from Winters’ work at Google and his current research and productivity focus at Adobe. The publication describes him as having spent more than a decade at Google and as the lead author of Software Engineering at Google. It says the episode addresses a broad set of topics, including the company’s refactoring project, testing requirements, readability reviews, AI productivity and ways new engineers can distinguish themselves.
The refactoring account is notable for its engineering method. Rather than editing millions of lines by hand, the team used language parsing and automated edits, while arranging for old and new APIs to coexist during migration. The source says the clang-format toolkit arose from needs encountered during this work. The process was designed around controlled batches and preventing the old pattern from being reintroduced.
At Google, the readability program formalized language-specific review and mentoring. The source reports that more than 10,000 engineers were enrolled at a given time when Winters left the company. That figure describes participation in the program, not a measure of its outcomes or a comparison with other training programs.
“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
What the Interview Does Not Establish
The supplied report does not provide a publication date for the episode, the full transcript, or Winters’ specific proposed changes to the ACM/IEEE curriculum guidelines. The promotional description that he wants to “burn down almost all” of the curriculum is not accompanied here by details sufficient to establish exactly what he would remove or replace.
The source also does not independently verify the reported relationship between Google’s testing mandate and its later shipping cadence. Its AI-related outage figures are presented as Winters’ observations from conversations with engineers at other companies; no dataset, sample size, measurement period or comparison baseline is supplied. They should not be treated as a general industry statistic.
The Curriculum Debate Continues
The episode is available through YouTube, Apple and Spotify, and the source says a transcript and episode timestamps are available on its page. Those materials would provide the fuller detail needed to assess Winters’ arguments about AI, productivity and the undergraduate curriculum.
No formal curriculum change, adoption timeline or next decision point is identified in the supplied report. The next concrete development to watch for is further detail from Winters or the ACM/IEEE process on which curriculum recommendations may change and how those proposals would be considered.
Key Questions
Who is Titus Winters?
Titus Winters is a software engineer and researcher who spent more than a decade at Google, where he led its readability program and helped build Abseil. The Pragmatic Engineer describes him as a senior principal scientist at Adobe, focused on developer experience and productivity.
What is the news development?
The Pragmatic Engineer published a podcast conversation with Winters about software engineering at Google, computer science education, AI and engineering productivity. The supplied source does not specify the episode’s publication date.
What did the Google refactoring project involve?
Winters described a 2010 effort to replace an old C++ API across a codebase the source says was close to 250 million lines. The team used parsing, automated code edits and staged migration techniques to make changes while the software remained in use.
Does the source prove that AI is increasing software outages?
No. The report attributes an observation to Winters based on conversations with engineers at other companies. It provides no sample size, measurement window or baseline, so the account does not establish an industry-wide increase.
What changes to computer science education are proposed?
The source says Winters has worked on updating ACM/IEEE undergraduate computer science curriculum guidelines, but it does not detail his specific proposals or identify an approved revision. The episode transcript may offer more detail.
Source: newsletter.pragmaticengineer.com
