TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The Pragmatic Engineer published a podcast interview with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, about engineering practices and computer science education. The conversation covers a major C++ refactor, Google’s testing and code-review programs, and Winters’ views on AI and what students should learn; the supplied report does not include the full discussion or the specific curriculum proposals.
The Pragmatic Engineer has published a podcast interview with Titus Winters, a former Google engineer and lead author of Software Engineering at Google, discussing how large engineering organizations manage code and why computer science education may need revision. The conversation draws on Winters’ experience with Google’s C++ codebase and engineering programs, while also touching on AI’s effects on software work.
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. The report says he is now a senior principal scientist at Adobe, working on developer experience and productivity. The interview was published as an episode of The Pragmatic Engineer podcast, with listening and viewing options listed on the original report.
A central example is a company-wide C++ refactoring effort that Winters joined in 2010. According to the report, Google then had nearly 250 million lines of code, maintained by about 10,000 engineers. A team of roughly a dozen people used language parsing and automated code changes to replace old patterns while keeping the codebase in use. The process included parsing build targets into syntax trees, generating edits, and rolling changes out in batches. The report says the work also led to the creation of the clang-format toolkit.
The interview also revisits Google’s engineering safeguards. Winters described a company mandate that changes include tests, introduced after Search struggled to release as frequently as it had before. The report says Google’s code-review approach required approval from both a project or file owner and a language-trained readability reviewer. It says more than 10,000 engineers were enrolled in readability when Winters left Google, about three months before the report was written.
Engineering Practices at Google’s Scale
The examples matter because they show how testing, review and automated refactoring can support change across a large, interconnected codebase. The source describes safeguards not just as ways to catch defects, but as conditions that can make maintenance safer for engineers. That perspective is relevant to organizations weighing delivery speed against the risks of changing systems on which many products depend.
The education discussion connects those workplace practices to the preparation of new engineers. Winters worked on updating the ACM/IEEE undergraduate computer science curriculum guidelines, according to the report. The available material signals disagreement with parts of traditional coursework, but does not detail the proposed changes. Readers should distinguish that stated position from a settled account of what universities should teach.
The interview also raises a question about how to evaluate AI-assisted software development. The report attributes to Winters an observation that engineers he speaks with are producing substantially more code, while outages are also up and feature output is static. That is an anecdotal assessment as presented in the source, not a systematic industry-wide measurement.
Products Worth Considering
Apple iPad Air 11-inch (M2), 512GB, Wi-Fi, Space Gray
Apple AirPods Pro 3 Wireless Earbuds
EcoFlow Smart Home Panel 2 Whole-Home Backup System Hub
As an affiliate, we earn on qualifying purchases.
From Google’s Codebase to CS Curricula
The interview brings together two strands of Winters’ work: engineering systems inside a large technology company and the education of future software developers. His book, Software Engineering at Google, is the basis for the report’s description of his role as its lead author. The discussion uses Google’s history to examine how code review, testing and maintenance practices operate at scale.
The source recounts that Google’s Search product had difficulty maintaining a monthly release cadence around 2007, with quarterly releases described as the best the team could manage at the time. It says Google responded by requiring tests for changes, and that Search later returned to a faster cadence. This is the report’s account of the sequence; it does not provide release data or a separate evaluation of the policy’s effect.
Winters’ curriculum work concerns guidelines developed through the ACM and IEEE, professional organizations involved in computing education. The supplied report frames the interview around a call to rethink much of the curriculum, but its excerpt ends before laying out the detailed case or the proposed syllabus changes.
“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, as quoted in The Pragmatic Engineer report
Curriculum and AI Claims Need Detail
The supplied source excerpt does not state which parts of the computer science curriculum Winters believes should be removed, what should replace them, or whether the ACM/IEEE guideline revision has been adopted. It also does not provide a transcript of the full discussion, so the framing that the curriculum should be almost entirely discarded cannot be assessed beyond the report’s summary.
The report attributes an approximately 30% rise in outages to Winters’ conversations with engineers at other companies. It gives no sample size, measurement period, definition of outage or comparison method, and does not establish that AI caused the reported change. The claim should be treated as an observation reported in the interview, not as a verified industry statistic.
The source also refers to AI increasing code output, but the excerpt cuts off before presenting the rest of Winters’ analysis. The scale of any productivity gains, the affected roles and the implications for entry-level engineers remain unclear in the material provided.
Full Interview and Curriculum Proposals
Readers seeking Winters’ complete reasoning can consult the full episode and transcript linked by The Pragmatic Engineer. The next useful milestone for the education discussion is a clearer account of the specific ACM/IEEE curriculum recommendations, including their status and how they differ from existing guidance.
For the AI discussion, firmer conclusions would require transparent data on code output, outages and feature delivery across a defined period, with comparable organizations or teams and a stated method. The supplied report does not announce a follow-up study or a timetable for curriculum changes.
Key Questions
What is the news about Titus Winters?
The Pragmatic Engineer published a podcast interview with Winters about software engineering at Google, computer science education and AI’s effects on development work.
What did Winters do at Google?
The report says he spent more than a decade at Google, led its readability program and helped build Abseil, an open-source collection of foundational C++ libraries.
What was the large C++ refactoring project?
According to the report, a team of about a dozen engineers used parsing and automated edits to update code across a Google codebase described as nearly 250 million lines in 2010, without taking the systems out of service.
Does the report establish that AI has increased outages by 30%?
No. It reports Winters’ observation from conversations with engineers, but supplies no sample, time window or method and does not establish that AI caused the outages.
What changes to computer science education does Winters propose?
The supplied excerpt says he worked on updating ACM/IEEE undergraduate curriculum guidelines and questions traditional coursework, but it does not specify which subjects he would remove or add.
Source: newsletter.pragmaticengineer.com
