Prioritizing Technical Debt as if Time and Money Matters
summary
A methodical claim: version-control history plus simple complexity metrics expose where refactoring pays off. Uses a hotspot visualization on Android’s 3M‑LOC platform framework base to find the head of the power‑law curve; isolates ActivityManagerService (20k LOC) and its 500‑line handleMessage function that sees 98 commits/year and requires ~106 unit tests. An x‑ray splits files to function level, CodeScene/Codemap automate trends and simulate knowledge loss, so teams prioritize high‑change, low‑health hotspots and pair to transfer knowledge.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:30The problem
- 4:38Quantifying technical debt
- 8:54Hotspot visualization
- 16:48Activity Manager Service
- 19:30Why Hotspots Work
- 23:15Legacy Code
- 25:23Behavioral Code Analysis
related talks
39mArch. App: Prioritizing Technical Debt as if Time and Money Matters
20mPrioritizing Technical Debt as if Time and Money Matters
30mPrioritizing Technical Debt as if Time and Money Matters
50mGuide Refactorings With Behavioral Code Analysis
36mPrioritizing Technical Debt as if Time & Money Matters
45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI Issues
39m7 Secrets of Maintainable Codebases
40mTreat Your Code as a Crime Scene