Living With Technical Debt: Acknowledge It, Specify It, Reduce It

on YouTube ↗25m

" summary

Survey data shows two-thirds of teams have a “scary” code area and unplanned work ranges 10–80% of time, creating measurable slowdown. Treat technical debt as a lifecycle: acknowledge, specify, reduce — log issues in trackers, add tests to make problems visible, use code-quality metrics to find long functions and coupling, do safe renames and small helper refactors as quick wins, and prioritize fixes by importance, risk to change, and implementation cost.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 0:41Team frustrations
3. 2:44What is technical debt?
4. 7:192 Concrete Debt
5. 10:56Cultural approach to technical debt
6. 14:38Antipatterns

" related talks

• 35mTechnical Debt. A guide for developers and IT managersLaurentiu Spilca · Voxxed Days Iași 2023
• 45mTechnical Debt: Taking back control when it's already messed upChristopher Cacciatore · Voxxed Days Luxembourg 2026
• 28mManaging Technical Debt at ScaleWerner Heijstek · DevOpsDays Eindhoven 2022
• 25mDemystifying Technical DebtEgon Elbre · GopherCon Europe 2021
• 36mPrioritizing Technical Debt as if Time & Money MattersAdam Tornhill · GOTOpia Europe 2020
• 45mA developer always pays his debtsJulien SOLEILHAVOUP · AFUP Day 2020 Lyon
• 30mPrioritizing Technical Debt as if Time and Money MattersAdam Tornhill · DevBreak 2021
• 41mA Bluffer's Guide to Technical Debt for Other PeopleSteve Freeman · Heapcon 2019