CONCEPT
Technical Debt
Ward Cunningham's 1992 metaphor for the cost of expedient decisions in software — now reshaped by AI into a new variant: the debt of implicit decisions that were never evaluated against a consistent design.
Ward Cunningham introduced the metaphor of technical debt in 1992 to explain to his non-technical managers why shipping code quickly sometimes carried long-term costs. Just as financial debt allows immediate spending in exchange for future interest payments, technical debt allows immediate shipping in exchange for future maintenance costs. Well-managed technical debt — incurred deliberately, documented, and paid down systematically — can be a rational strategy. Unmanaged technical debt accumulates compound interest, as subsequent work becomes slower and more error-prone because the foundation is not what it should be. The metaphor became orthodox in software engineering precisely because it made an invisible cost visible to non-technical stakeholders who had been unable to see it.
In The You On AI Field Guide
AI produces a new variant of technical debt, specific to AI-generated codebases. In team-based development, technical debt accumulated because different team members made different assumptions, or because expedient shortcuts were taken deliberately under schedule pressure. In AI-augmented development, technical debt accumulates