Guides
Practical, hands-on guides to Engineering Intelligence and AI-assisted software development — how to read, question, and genuinely learn from the code AI writes for you. Each guide turns a single habit or concept into steps you can apply on your next pull request, so shipping fast and understanding deeply stop pulling in opposite directions.
People use AI to learn. Software engineering is where that breaks.
Google's ATLAS report shows people reach for AI to understand things, at a rate that outstrips almost everything else. Coding is the exception — and the cost is knowledge debt.
What is AI comprehension? Understanding the code AI writes for you
AI comprehension is how well an engineer understands AI-generated code — the reasoning, trade-offs, and failure modes behind it, not just that it passes.
Knowledge Debt vs Technical Debt: What's the Difference?
Technical debt is code that's costly to change. Knowledge debt is code no one fully understands. Here's how they differ — and why AI widens the gap.
Engineering Intelligence: measuring what your team actually understands
Engineering Intelligence is the practice of measuring and growing what engineers genuinely understand about the code they ship — not just how fast they ship it.
How to actually learn from AI-generated code
A practical guide to understanding the code AI writes for you — five habits that turn AI-assisted shipping into lasting engineering knowledge.