Taming your Dragon: Addressing your technical debt beast
summary
Claim: technical debt is a human trade‑off problem driven by biases, emotion and role incentives rather than a pure engineering flaw. Cites a dice gamble where ~60% choose risk and a tiny 5 cent change reverses behaviour, models an epidemic (SIR) and a three‑project software simulation that saves about £1.3M on project one but increases total cost later, and uses Venim system dynamics models to explore interventions.
AI-written summary · about
chapters (11)
- 0:00Technical debt basics
- 3:18Technical debt is not technical
- 7:37Emotions and technical debt
- 11:35Emotions to manage debt
- 13:17Decisions in organizations
- 15:25Unintended system changes
- 18:17Dynamic systems models
- 21:07Modeling technical debt
- 23:37Wicked problems solutions
- 24:41Targeted debt approaches
- 25:05Q&A
related talks
28mTechnical Debt: Why it'll ruin your software
34mThe Technical Debt Trap
35mTechnical Debt. A guide for developers and IT managers
26mTech debt as innovation, reframing this forever problem as an opportunity
25mDemystifying Technical Debt
06mManage your tech debt like a mortgage
39mThe cash value of technical debt - How to scare your boss into doing the right thing
39mTechnical debt isn't technical