How to Start Refactoring Someone Else's Code Without Getting Fired in a Month
summary
A speaker describes practical strategies for refactoring someone else’s legacy JavaScript code without burning out or getting fired, explaining how they balanced adding new features while incrementally modernizing old code. The talk recounts specific painful experiences, lessons learned about taking time to understand large files, and why legacy code can be an opportunity to improve one’s skills.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:55Legacy code analysis
- 12:08First week paralysis
- 14:39Code analysis via docs
- 22:13Refactoring as learning
- 24:26Minimal changes
- 28:46Step-by-step refactoring
- 32:06Task analysis
- 36:10Refactoring tips
- 37:45Closing remarks
- 38:11Q&A
related talks
30mHow to Refactor and Stay Alive? (Refactoring Client Code)
31mAre you a selfish programmer? - Refactoring (...)
48mThree Principles To Bring Your Legacy Code Into the Future
55mHow To Approach Refactoring
59mRefactoring a Complex Project Live
57mUnlocking The Awesome Power of Refactoring
35mQuickly and Safely Refactoring Legacy Code
01h 00mHow to Approach Refactoring
