Loving Legacy Code
summary
Defines legacy code as anything that impedes change, shows a concrete example of a Rails model with 104 methods, and argues automated unit tests plus breaking dependencies enable safe refactoring. Recommends tools like RuboCop, Code Climate, New Relic and Buildkite, practical fixes such as splitting slow CI into parallel steps, removing flaky feature tests, adding solitary unit tests, and using git and GitHub pull requests to spread knowledge and reduce bus factor.
AI-written summary · about
chapters (8)
- 0:00Intro
- 4:42Identifying pain points
- 6:18Improving the code
- 9:52Refactoring
- 14:04Tools
- 16:07Attitude
- 17:49Developers
- 21:22Metaphors
related talks
28mHarry Potter and the Legacy Codebase
20mWhat were they thinking?
39mDown The Rabbit Hole: An Adventure in Legacy Code
36mWorking Compassionately with Legacy Code
34mTesting legacy code when you dislike tests (and legacy code)
28mRESCUE SQUAD: Rails Edition!
01h 25mGetting a Handle on Legacy Code
36mUsing Tests as a Tool to Wrangle Legacy Projects