technical-debt

Technical debt is a human-made conceptual metaphor in software engineering that frames accumulated code quality degradation as a financial debt instrument. The metaphor maps development shortcuts — writing quick solutions instead of well-architected ones — to borrowed capital that accrues interest in the form of increased future development cost, reduced adaptability, and higher defect rates. It persists through developer awareness, documentation of known shortcuts, prioritization frameworks that weigh refactoring against feature work, and the recurring tension between delivery speed and code quality. The construct is not literal debt: no creditor exists, no principal is owed, and the interest rates are estimated, not contractual. Its power lies in making abstract quality trade-offs legible to both engineers and non-technical stakeholders. [formal: technical debt | substrate: mind | horizon: hours | explicit: no | epoch: 0.95]