Tech debt as innovation, reframing this forever problem as an opportunity
summary
Claim: technical debt is a natural by‑product of software innovation and can be an innovation vehicle when treated specifically. Examples: modernising a 17–18 year old NCCP protocol instead of abandoning it, running three API stacks in production, and funding a device‑retirement program. Tools and projects: ICFD (increase confidence and frequency of deployments), platform migration teams, and a confidence‑chimp style chaos approach. Results: 20+ cross‑functional tracks tackle fleetwide changes, migrations run 7+ years, and targeted investment extends system life and deployment speed.
AI-written summary · about
chapters (10)
- 0:00Introduction and philosophy
- 1:19Origin of the concept
- 2:39Identifying common issues
- 4:49Defining debt principles
- 7:12Proactive management
- 8:45Strategic funding and projects
- 13:07The migration trap
- 15:52Case study in timing
- 16:38Innovation and myth-busting
- 24:22Final takeaways
related talks
35mTechnical Debt. A guide for developers and IT managers
45mTechnical Debt: Taking back control when it's already messed up
28mTechnical Debt: Why it'll ruin your software
31mTech Debt: Leverage for velocity acceleration
34mThe Technical Debt Trap
01h 01mThe Technical Debt Prevention Clinic
53mRewrite or Not? Life with Technical Debt
57mPutting an end to "technical debt"