Technical Debt: Taking back control when it's already messed up
summary
This talk explains how to regain control of a codebase overwhelmed by technical debt by diagnosing its causes, prioritizing fixes, and applying concrete remediation techniques. It covers practical strategies such as incremental refactoring, automated testing and CI, dependency management, and governance changes to prevent recurrence.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 7:00Technical debt vs defects
- 13:40Software entropy and complexity
- 21:06Convincing Jean-Guy
- 32:14Analysis and decision report
- 36:06Resolution and results after 18 months
- 39:22Conclusion
- 41:55Q&A
related talks
35mTechnical Debt. A guide for developers and IT managers
34mThe Technical Debt Trap
28mTechnical Debt: Why it'll ruin your software
25mLiving With Technical Debt: Acknowledge It, Specify It, Reduce It
01h 01mThe Technical Debt Prevention Clinic
18mTechnical Debt: How to Communicate to Teams, Beyond the Tech
51mTechnical Debt as Theory Building and Practice
53mRewrite or Not? Life with Technical Debt