The Art of Refactoring
summary
Live demo refactors a deliberately broken collection library using IntelliJ automated refactorings, converting object arrays to Lists, extracting methods and running 48 tests as a safety net; a wrong large step creates a bug that tests catch and forces a graceful rollback. Managers get convinced by a printed 28-page function and automated smoke tests. Advice: take small safe steps, profile if performance matters, prefer encapsulation/wrappers over toggles, and use tools but expect them to sometimes misbehave.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:17What is refactoring
- 3:53Tension between development and business
- 5:06The Scroll
- 7:43Less moving parts
- 10:00I cant make everything simple
- 10:36I cant make everything perfect
- 12:13Live refactoring
- 14:31Making code readable
- 19:00Performance
- 20:50Readonly setter
- 23:55Map
- 24:42Lists
- 26:44Refactor Safely
- 30:20Set Value at
- 31:32Getters
- 32:42GetValue
- 34:17GetValue at
- 36:48Test Failure
related talks
55mHow To Approach Refactoring
35mRefactoring Frenzy - Don't settle for short term
57mUnlocking The Awesome Power of Refactoring
35mQuickly and Safely Refactoring Legacy Code
54mGet better at Refactoring
50mRefactoring Is Not Just Clickbait
46mThe Surprising Effectiveness of Small Steps
37m47 Refactorings in 45 minutes