The Secrets of Successful Refactoring
summary
Presents evidence from GitLab that successful refactoring relies on clear ownership (one individual owner per refactor), persistent notifications and documentation, plus automation. Describes using jscodeshift and ts-morph for large automated codemods that convert ~80–85% of sites with ~15% needing manual fixes, and using ESLint rules and test/automation gates to prevent regressions and increase completion rates beyond the typical 30–40% finished within two years.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:18Refactoring stalls
- 6:25What refactoring is
- 10:23Murphy’s Law for refactoring
- 13:38Organizing refactoring
- 15:47Selling refactoring
- 17:53Convincing programmers
- 18:56Automated refactoring checks
- 20:05Mediocre code
- 24:25Tricky refactorings
- 27:14Breaking down tasks
- 27:57Architectural refactoring
- 30:18Q&A
- 31:43Q&A
- 33:30Q&A
related talks
35mQuickly and Safely Refactoring Legacy Code
55mHow To Approach Refactoring
40mRefactoring large JavaScript codebases
57mUnlocking The Awesome Power of Refactoring
50mRefactoring Is Not Just Clickbait
45mPanel Discussion Refactoring
40mHow To (Semi-)Automate JavaScript Refactoring
48mThree Principles To Bring Your Legacy Code Into the Future
