You Thought Technical Debt Was the Worst? Meet Design Debt!
summary
The talk examines design debt (accidental design debt) as a deeper cause behind persistent technical debt, explaining how practices like KISS and YAGNI can sometimes worsen the problem. It describes how design debt leads to tangled codebases and “distributed monolith” microservices, and shows concrete ways to detect, assess its severity, and intervene to prevent it from becoming entrenched.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:28Spaghetti model effects
- 8:18Business model decay
- 11:30Layered model coupling
- 17:24Model tensions and bias
- 23:14Model tensions in code
- 29:13Service coupling
- 33:43Distributed monoliths
- 38:14Organizational tensions
- 42:05Conway's law solutions
- 44:51Conclusion
related talks
35mTechnical Debt: When Interest Eats Your Code
15mThe Truth About Technical Debt
25mDemystifying Technical Debt
35mTechnical Debt. A guide for developers and IT managers
45mA developer always pays his debts
45mTechnical Debt: Taking back control when it's already messed up
39mTechnical debt isn't technical
48mManaging Architectural Debt in a Hypergrowth Context