Technical Debt. A guide for developers and IT managers
summary
Technical debt increases with entropy even if code is untouched and can reach technical bankruptcy where rewriting is the only option; one audited company later goes bankrupt. A successful pattern loans time: ship a minimum viable replacement in 8 months, log every shortcut in the backlog, measure and prioritize debt, and insist stakeholders allocate payback time. Follow the Boy Scout rule (fix small messes on sight), include debt items in the Definition of Done, and avoid over-polishing at the wrong cost.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06What is technical debt
- 3:56Technical bankruptcy case
- 7:51Technical debt strategy
- 15:21Rules for managing debt
- 24:45Clean code vs profitability
- 29:16Key conclusions
- 30:20Q&A
related talks
34mThe Technical Debt Trap
28mTechnical Debt: Why it'll ruin your software
01h 01mThe Technical Debt Prevention Clinic
45mTechnical Debt: Taking back control when it's already messed up
25mDemystifying Technical Debt
25mLiving With Technical Debt: Acknowledge It, Specify It, Reduce It
31mDealing with Technical Debt
28mManaging Technical Debt at Scale