The cash value of technical debt - How to scare your boss into doing the right thing
summary
Quantifies technical debt as friction that turns 10 developers × 6 months ($500k) of work into a liability not an asset, models debt compounding with a spreadsheet using the standard effective annual rate formula, reports an example 20,000% effective interest and velocity falling to ~58% (dangerous below 50%), shows refactoring every few sprints dramatically raises efficiency (32% → 73%), and emphasizes refactor early refactor often as the control.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 0:41Defining technical debt
- 17:43Modeling debt impact
- 21:36Refactoring strategies
- 31:54Q&A session
related talks
35mTechnical Debt. A guide for developers and IT managers
34mThe Technical Debt Trap
31mTech Debt: Leverage for velocity acceleration
27mUnveiling the Business Value of Technical Debt
28mTechnical Debt: Why it'll ruin your software
25mDemystifying Technical Debt
31mDealing with Technical Debt
46mStop calling it technical debt and listen to your engineers