How to work with legacy so neither you nor the project burns out
summary
Explains what legacy code is, how legacy systems arise, and when refactoring is genuinely necessary. Describes how to estimate the costs of refactoring and presents methods and approaches for performing safe refactoring in production systems.
AI-written summary · about
chapters (17)
- 0:00Legacy introduction
- 1:09What is Legacy
- 3:04Legacy causes
- 4:07Technical debt effects
- 6:16Business Legacy problems
- 7:19Team Legacy problems
- 9:47Refactoring signs
- 12:59Subjective metrics
- 14:01Objective metrics
- 20:22Code analysis tools
- 25:16Task prioritization
- 30:18Refactoring prep
- 33:51Selling refactor to business
- 36:59Change plan & rollout
- 39:07Avoiding new Legacy
- 40:58Recommendations & takeaways
- 42:10Q&A
related talks
01h 11mLegacy: Rewrite cannot support
52mOMG, What a Beautiful Legacy
50mWe ♥️ legacy
51mThe Void of Legacy: A Strategy for Radical Improvements in a Project
54mThe Future of the Past – Legacy Will Stay With Us
03mENTREVISTA
36mWorking with Legacy Erlang Code
50mMistakes I made working with legacy code and how to fix them