Congratulations! Legacy Code GURU Level Unlocked!
summary
Static analysis flags cyclomatic complexity, coverage gaps and an A–E quality rating while a Sonar run on an open repo surfaces ~43 outstanding issues; behavioral analysis then maps change frequency to real pain by finding hotspots—one file shows 125 edits—and exposes temporal coupling that forces simultaneous edits across modules. Case studies contrast a full iOS rewrite with incremental refactors, and practices proven effective include a technical debt committee, dedicated “technical debt days” and visualizing history with gource to prioritize what actually slows teams.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 6:05Defining technical debt
- 10:15Tactical decisions
- 13:56Static code analysis
- 21:47Technical debt committees
- 25:26Behavioral code analysis
- 37:23Conclusion and wrap-up
related talks
53mCongratulations! Legacy code guru level unlocked!
01h 31mClean(er) Code for Large Scale Legacy Applications
24mRichard Gross Head of Software Archeology, MaibornWolff
54mThe Future of the Past – Legacy Will Stay With Us
41mDomain Re discovery Patterns for Legacy Code
51mThe Void of Legacy: A Strategy for Radical Improvements in a Project
35mTaming Legacy: Refactoring Patterns for Large Flutter Codebases
26mLegacy Codebases are a DevOps Issue