Tackling Tech Debt on Android
summary
Defines tech debt as code that erodes confidence and recommends measuring items by impact/effort/contagion so high-impact low-effort low-contagion items get priority; uses Android examples (target SDK forced updates, legacy networking stacks) as opportunities to batch fixes. Prescribes a ticket template and team workshop to catalog and rank debt, insists on tiny refactors with no behavioral change and write tests first (or tiny refactor to enable tests), and suggests you can fold debt into estimates or pick ranked items for spare sprint time.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:08Legacy code reality
- 3:20Tech debt origins
- 5:50SDK updates opportunity
- 7:17Identifying tech debt
- 9:00Prioritizing impact and effort
- 12:09Contagion of debt
- 14:14Planning and organizing
- 18:07Convincing managers
- 20:57Refactoring success
- 27:35Team burden reduction
- 28:45Q&A
related talks
36mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
39mI don't have any technical debt
34mThe Technical Debt Trap
06mManage your tech debt like a mortgage
31mDealing with Technical Debt
23mCan We Please Stop Talking About Tech Debt?
01h 01mThe Technical Debt Prevention Clinic
35mTechnical Debt. A guide for developers and IT managers