No More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
summary
Sixty Android engineers, ~550 modules, and ~300 PRs/week drive a concrete system that visualizes and prioritizes tech debt: a one-month prototype by a single engineer pulls issues via the SonarQube API, stores them in a simple mobile-metrics service, and renders team and module dashboards in Metabase with a 0–5 Health Score and drill‑down to file and IDE links. Results: an aim of 90% of teams halving debt in six months is met in under three months, with weekly CI auto‑fixes and an IDE plugin and AI-assisted fix flow planned.
AI-written summary · about
chapters (9)
- 0:00Tech debt at Konto
- 2:49Scaling challenges
- 7:48Prototype solution
- 15:58Beta testing feedback
- 17:21Driving team adoption
- 20:55Health board demo
- 26:42Key learnings
- 31:20Future automation goals
- 34:54Conclusion
related talks
36mNo More "Someone Else’s Problem": Tackling Tech Debt at Scale
40mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
33mTackling Tech Debt on Android
30mPrioritizing Technical Debt as if Time and Money Matters
47mGamifying Reduction of Technical Debt
45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI Issues
20mPrioritizing Technical Debt as if Time and Money Matters
11mRefactoring: Managing technical debt before it blows up in your face