chapter one

1 The shift: Code is free now. Understanding isn't.

 

This chapter covers

  • Comprehension debt: the gap between code you ship and code you understand
  • Coder mode vs engineer mode: generating code vs understanding it
  • Using AI to understand a codebase, not just generate more code
  • Architectural thinking: the 10% skill AI can't replace
  • Turning AI's flaws into reps that sharpen your judgment

AI tools have made writing code significantly easier, a practice often called vibe coding. In vibe coding, you describe a feature to an AI, let it generate the code, and then ship it with minimal review. This approach is common: GitHub reports that Copilot writes nearly half the code in files where it's enabled. Boris Cherny, who developed Claude Code, even completed a month of work (259 pull requests and roughly 40,000 lines) without opening his editor, generating every line with AI (https://fortune.com/2026/06/11/anthropic-claude-boris-cherny-doesnt-write-code-by-hand-anymore/). This book, however, focuses on the other side of the equation: using AI to understand code, especially systems you didn't write and can't yet explain, rather than just generating more of it.

1.1 The problem: Comprehension debt is the silent killer

1.2 The reframe: From reading code to architectural thinking

1.2.1 The 90% skill is a commodity. The 10% is your muscle.

1.2.2 The 10% muscle: Use it or lose it

1.3 The multiplier: How to "work out" with AI

1.3.1 Three questions you can run today

1.3.2 The coder gets code. The engineer gets stronger.

1.3.3 What an engineering rep looks like

1.4 "But AI hallucinates..."

1.5 The book's path: Layer-by-layer reverse-engineering, not framework tours

1.6 Summary