Engineering brief

Why CS Education Must Burn Down and Let AI Change the Game

The Pragmatic Engineer2 min read · saves 99 min

At a glance

The brief is enough

Relevance
Practical value
Radar
Time horizon
This year
Warnings
None

Titus Winters on Google's 250M-line refactoring: deterministic tools beat AI for large-scale changes. CS curricula need to grade prompts and tests, not code.

AI's real value is enabling harder problems, not faster output. CS education must shift from code to process.

Watch if you want deep detail on Google's readability process or refactoring tooling.

Summary

The refactoring feat. Google's 250 million line C++ monorepo was cleaned by a small team using compiler-assisted AST transformations, not AI. This remains the largest refactoring in history. The lesson: deterministic tooling (like OpenRewrite) is cheaper and more reliable than AI for large-scale code changes.

The education program. Google's readability program, which Titus oversaw, was a massive mentoring effort that taught idiomatic code through review. Tens of thousands participated. This shows that code consistency and education can scale through process, not just tooling.

Where AI adds value. Titus argues that productivity metrics (code output, features) miss AI's real impact: enabling teams to tackle harder, previously impossible problems. Example: writing a JPEG parser in weeks. The value isn't doing the same things faster but changing the game.

CS education crisis. Most CS curricula haven't changed since 2000. With AI, students can produce slop without understanding. Titus advocates grading prompts and tests instead of code, and shifting from implementation to specification, design, and validation. The middle of the bell curve is collapsing.

Team dynamics endure. Psychological safety and learning culture remain the strongest predictors of team success. AI doesn't change that. In fact, the shift to managing agents makes communication and clarity even more critical.

The path forward. Titus suggests CS enrollment may drop, replaced by software engineering programs focused on practice, teamwork, and domain expertise. The advantage is no longer raw coding speed but deep problem understanding and the ability to evaluate AI outputs.

My take

I've seen similar patterns: the most valuable refactoring work at my org used deterministic codemods, not AI. Titus's insight that CS education must grade process over artifact resonates deeply. But I'm skeptical that enrollment will plummet, demand for engineering talent remains high if graduates can demonstrate judgment. The real risk is that universities fail to adapt, leaving a gap that bootcamps or internal training fill. What I'd watch: whether companies start requiring candidates to show how they used AI in a project, not just the output. The 10x engineer narrative is dangerous because it ignores the team dynamics Titus emphasizes. The best AI-augmented teams still depend on psychological safety and learning culture.

What to do with this

  1. Audit your refactoring workflow: replace AI-only approaches with deterministic codemods where possible.
  2. Redefine productivity metrics to capture new capabilities enabled by AI, not just output volume.
  3. Update your hiring rubric to evaluate how candidates use AI, focus on process and judgment over output.

Watch the video

This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.

Related breakdowns

Get TL;DW

Too Long; Didn't Watch.

A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.

Free. Weekly. No hype.

Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.