Balancing Technical Debt and Modernisation in DevOps

on YouTube ↗05m

" summary

Argues that migration succeeds when teams map specific legacy quirks, run vulnerability and risk assessments, and schedule work so features keep shipping while debt is paid down. Cites Kubernetes removing 450,000 lines removed as evidence everyone accrues debt. Recommends incremental refactoring over Big Bang, plus hybrid and debt‑driven options, explicit resource allocation, planned downtime windows, stakeholder signoff, measurable prioritization by impact and urgency, and integrating fixes into the DevOps pipeline.

AI-written summary · about

" related talks

• 28mManaging Technical Debt at ScaleWerner Heijstek · DevOpsDays Eindhoven 2022
• 34mThe Technical Debt TrapDoc Norton · Rocky Mountain Ruby 2014
• 33mTackling Tech Debt on AndroidTy Smith, Kate Kelly, Joaquim Verges · droidcon San Francisco 2018
• 18mTackling tech debtMeri Williams · LeadDev New York 2025
• 11mRefactoring: Managing technical debt before it blows up in your faceAmanda Sopkin · LeadDev New York 2022
• 28mTechnical Debt: Why it'll ruin your softwareLuan Fonseca · DjangoCon US 2019
• 19mHalt and Don’t Catch FireEffie Mouzeli · SREcon18 Europe/Middle East/Africa
• 30mWhy most technology migrations fail (and what we've learned along the way)Jai Chakrabarti · LeadDev New York 2022