Cognitive Debt
Definition
The gap between what code does and what developers understand about the code. Coined by Margaret-Anne Storey (February 2026). Unlike technical debt, which lives in the codebase, cognitive debt lives in the developer's head. Even if AI agents produce code that could be easy to understand, the humans involved may have simply lost the plot — they may not understand what the program is supposed to do, how their intentions were implemented, or how to change it. Cognitive debt compounds silently: each AI-generated session adds working code that the developer didn't write and may not fully comprehend. Published as part of a convergent moment where five independent groups identified the same structural problem in one week (February 15-21, 2026).
Builder Context
Cognitive debt is the hidden cost of agentic coding that nobody budgets for. The symptom: you look at code your agent wrote 3 sessions ago and can't explain why it's structured that way. The fix: (1) never let agents code without specifications — Spec-Driven Development creates the understanding map before code exists; (2) require agents to document WHY decisions, not just produce code; (3) conduct regular 'comprehension audits' where you explain each component's purpose without reading the code; (4) treat unexplainable code as a bug, not a feature. Design systems reduce cognitive debt by constraining the decision space — when there are only 2 widths and 7 heading sizes, there's less to understand.