I don't have any technical debt
summary
Claims a production Android app used by millions of Norwegians (NRKTV, BankID context) reaches near-zero technical debt by cultural rules: developers own planning, treat code as product, and always clean a touched file. Concrete moves include migrating from Retrofit to Ktor in one PR with 126 files changed and 3,000 lines to remove old interceptors, heavy reliance on unit and screenshot tests, distrust of AI-generated code, and a rule that yields no code untouched over a year.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:55Android teams outpacing iOS in speed
- 4:39Defining technical debt
- 8:53Technical debt culture
- 9:38Systems cause debt
- 12:43Avoid unused code
- 14:09Code is the product
- 16:37Scope creep prevents debt
- 21:41Ask forgiveness not permission for technical fixes
- 24:29Debt is mindset
- 26:15Eliminating codebase fear
related talks
33mTackling Tech Debt on Android
40mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
47mGamifying Reduction of Technical Debt
39mTechnical debt isn't technical
31mDealing with Technical Debt
44mWhat are you Risking by Ignoring Technical Debt?
34mThe Technical Debt Trap
53mRewrite or Not? Life with Technical Debt