Prioritizing Technical Debt as if Time & Money Matters
summary
Shows how to use version-control data (commit history) to identify and prioritize technical debt by mining developers’ change patterns. Demonstrates a language-neutral hotspot approach with case studies that link complex, frequently changed code areas to high maintenance cost and show how quickly parts of a codebase can become legacy.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:36Lehman's "laws" of software evolution
- 3:50Technical debt
- 9:15Case study: Prioritizing technical debt
- 19:28Why hotspots work
- 23:41The legacy code link
- 26:07Case study: How quickly can you turn your current codebase into legacy code?
- 34:26Resources
related talks
20mPrioritizing Technical Debt as if Time and Money Matters
30mPrioritizing Technical Debt as if Time and Money Matters
45mTechnical Debt Prioritisation - Identifying & Fixing Highest ROI Issues
32mPrioritizing Technical Debt as if Time and Money Matters
01h 36mWorkshop: Tackling Technical Debt: An Analytical Approach
11mRefactoring: Managing technical debt before it blows up in your face
35mTechnical Debt. A guide for developers and IT managers
25mLiving With Technical Debt: Acknowledge It, Specify It, Reduce It