Tackling tech debt

on YouTube ↗18m

" summary

Advocates a concrete five step plan: visualize with DORA metrics and LinearB benchmarks, secure 50% time allocation and use API-first extraction from the monolith named Damos, plus Skiller Whale upskilling and architectural decision records for context. Claims a 40% improvement in cycle time and a cited ~450% throughput uplift while still shipping features, reports fewer incidents as services are pulled out, and warns rewrites take twice as long and can kill companies.

AI-written summary · about

" chapters (8)

1. 0:00Introduction and background
2. 1:12Defining technical debt
3. 2:57Context and legacy systems
4. 4:12Developer experience impact
5. 7:26A five-step plan for resolution
6. 11:24Executing the migration
7. 12:51Taming debt on a daily basis
8. 15:32Conclusion and final advice

" related talks

• 11mRefactoring: Managing technical debt before it blows up in your faceAmanda Sopkin · LeadDev New York 2022
• 29mAccelerate API Innovation: Secrets to Staying AheadAnna Daugherty · apidays London 2023
• 28mManaging Technical Debt at ScaleWerner Heijstek · DevOpsDays Eindhoven 2022
• 05mBalancing Technical Debt and Modernisation in DevOpsEmmanuel Ahaiwe · DevOpsDays London 2024
• 01h 02mTools for simplified large scale systemsAndrzej Grzesik, Wojtek Ptak · GeeCON 2024
• 52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & ScrumSander Hoogendoorn · GOTO Amsterdam 2023
• 54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile WorldSander Hogendoorn · Porto Tech Hub Conference 2024
• 25mCoherent impact: The art of strategyHazel Weakly · StaffPlus New York 2025