· ai-devtools

Design for Understandability

This is a talk I gave at Google's internal Code Health Summit in November of 2025.


I'm sharing it here in the hopes that it sparks further learning and discussion. In a world where LLMs generate much of our code, understanding that code is more important than ever.

But with a system as large and complex as Google's codebase, SWEs can easily fall into a pattern of learned helplessness where the best you can do is tweak the code and pray that it passes the tests. Without understanding, LLMs are little more than complexity-generating machines running at top speed.

There's a better way to go about this. Just as our industry has learned to design software for testability, we can also design it for understandability. We can use ideas like design by contract, class invariants, modularity, and more to create systems that we can understand one piece at a time, rather than piling more onto the big ball of mud and hoping it doesn't all collapse.

Earlier coverage

Related coverage

Also worth reading

  1. next.js 16.5.0-canary.59 released
  2. next.js 16.5.0-canary.56 released
  3. Presentation: AI-Assisted Software Delivery: From Code to Production
  4. Qualcomm offers test drive of its rack-scale Nvidia AI challenger
  5. Type inference and narrowing with reverse arrows