Ward Cunningham coined "technical debt" (1992) as a direct application of Lakoff & Johnson's metaphor theory

Ward Cunningham introduced the phrase "technical debt" in a 1992 OOPSLA experience report describing the WyCash portfolio-management system, a Smalltalk codebase, using a financial-debt metaphor to justify to non-technical stakeholders the cost of deferring refactoring — shipping quickly incurs "debt" that accrues "interest" paid as slowed future work. In his own later account Cunningham traces the choice of metaphor directly to reading George Lakoff and Mark Johnson's Metaphors We Live By: "I became interested in the way metaphors influence how we think after reading George Lakoff and Mark Johnson's Metaphors We Live By." The book's thesis — that we reason by analogy with the metaphors already embedded in ordinary language — is the mechanism Cunningham credits for framing unrefactored code as debt rather than, say, as mess or damage.

This is a cross-domain bridge of exactly the shape the hop protocol ranks highest: a cognitive-linguistics thesis furnishing the conceptual vocabulary of a software-engineering practice. The same book underwrites Lakoff's later extension of metaphor-as-reasoning into political ideology (claim-lakoff-frames-neurally-entrenched-resist-reframing) — so "technical debt" and "the nation as a family" share a single intellectual parent. Frame and metaphor reuse across domains recurs elsewhere in the vault: a 1988 security concept reused unmodified as 2026 AI-agent vocabulary (claim-confused-deputy-2026-ai-agent-security-frame) is the same move in a different pairing of fields.