I don't have any technical debt
summary
Claim: the Bank ID Android app used by millions of Norwegians becomes faster to change by treating technical debt as mindset not backlog item. Teams replace Retrofit with Ktor, run unit tests and screenshot tests, use collaborative PRs and a rule to touch a file, clean the whole file. A 13‑developer mobile org reaches rapid iteration by making developers code owners, embracing developer scope creep, and choosing ask forgiveness not permission for small refactors.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:54Android teams faster than iOS
- 5:21Redefining technical debt
- 7:08AI as tool not coworker
- 8:32Good products don't need perfect code
- 9:35Culture from developers bottom-up
- 11:01Systems create technical debt
- 13:32Code isn't great start over
- 14:56Meetings ruin productivity
- 17:03Scope creep prevents debt
- 19:57Pull request rules
- 21:46Ask forgiveness not permission for technical fixes
- 25:17Technical debt not real thing
- 27:03Own your codebase decisions
- 28:07Empower developers shape system
- 30:12Q&A
related talks
33mTackling Tech Debt on Android
31mDealing with Technical Debt
40mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale
35mTechnical Debt. A guide for developers and IT managers
26mTech debt as innovation, reframing this forever problem as an opportunity
34mThe Technical Debt Trap
53mRewrite or Not? Life with Technical Debt
01h 01mThe Technical Debt Prevention Clinic
