The Truth About Technical Debt
summary
Explains how the original metaphor of technical debt—as a pragmatic, temporary trade-off to reach short-term goals—has been distorted into a label for messy, untested, copy‑pasted code and large monolithic methods. Discusses how the concept is now measured by consultants and automatic tools in monetary terms, and argues that what people call “technical debt” is neither really debt nor purely technical.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:12State of the art
- 3:40Technical debt explained
- 5:02Development as translation
- 7:09Term origin and evolution
- 8:54Technical debt as externality
- 10:43Summary
- 11:04Q&A
related talks
25mDemystifying Technical Debt
35mTechnical Debt. A guide for developers and IT managers
51mTechnical Debt as Theory Building and Practice
28mManaging Technical Debt at Scale
45mYou Thought Technical Debt Was the Worst? Meet Design Debt!
41mA Bluffer's Guide to Technical Debt for Other People
49mDług techniczny - skryty oprawca organizacji nie tylko technologicznych
45mA developer always pays his debts
