Prioritizing Technical Debt as if Time and Money Matters
summary
Uses version-control mining and a hotspots visualization to prioritize real maintenance work rather than counting generic debt years. Applies Codesin and the open-source Codemat tooling and shows concrete results on Android platform/framework/base: a 20,000-LOC hotspot edited by 74 developers in three months, with a single function handleMessage: 500 LOC, CC=106, 98 edits/year identified as the high-impact refactor target. Claims a power-law edit distribution across ~300 codebases, so focusing frequent-change complex code buys measurable business value.
AI-written summary · about
chapters (6)
- 0:00Intro
- 0:36Lehman's "laws" of software evolution
- 2:04Technical debt
- 6:35Case study: Prioritizing technical debt
- 14:28Why hotspots work
- 18:35Resources
related talks
29mPrioritizing Technical Debt as If Time & Money Matters
30mPrioritizing Technical Debt as if Time and Money Matters
32mPrioritizing Technical Debt as if Time and Money Matters
39mArch. App: Prioritizing Technical Debt as if Time and Money Matters
36mPrioritizing Technical Debt as if Time & Money Matters
45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI Issues
11mRefactoring: Managing technical debt before it blows up in your face
36mNo More ‘Someone Else’s Problem’: Tackling Tech Debt at Scale