No More "Someone Else’s Problem": Tackling Tech Debt at Scale
summary
Company with 58 engineers, ~1,000 modules and 300 PRs/week builds a visibility pipeline that extracts SonarQube issues, stores them in an internal DB and renders team dashboards in Metabase; a CI job pushes realtime updates and deep links open files in Android Studio. It built a prototype in one month, uses SonarQube + Metabase + a CI job and added badges, quarterly coefficients and autofix jobs; result: 90% of teams cut tracked debt by ~50% in under three months.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 1:50Scaling challenges at Contour
- 3:15Tech debt visibility problem
- 5:25Defining success for solutions
- 7:10Ownership and data strategies
- 9:21Choosing Metabase
- 10:25Building Healthboard prototype
- 14:17Beta testing feedback
- 15:22Adoption strategies
- 17:05Refining scoring system
- 18:53Empowering teams
- 20:19Measuring success
- 21:02Live demo: Healthboard
- 25:17Key learnings
- 28:26Managing requests
- 30:14Balancing issue volume
- 31:16Expanding to iOS
- 32:59Automating debt reduction
- 35:15Conclusion
- 36:19Q&A
related talks
36mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
40mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
43mDeliver Fast with Confidence
47mGamifying Reduction of Technical Debt
34mScaling the Mountain: A Framework for Tackling Large-Scale Tech Debt
44mWhat are you Risking by Ignoring Technical Debt?
43mCode quality as an engine of your IT business
01h 12mBuilding a Technical Credibility to Fight Technical Debt