A summary and discussion of Martin Fowler's keynote 'Workflows of Refactoring' from OOP 2014. Fowler advocates for a continuous refactoring mindset rather than planned refactoring sessions, presenting Kent Beck's two-hats metaphor to separate 'adding function' from 'refactoring' modes. He categorizes refactoring workflows: TDD-driven, litter pickup, comprehension, preparatory, planned, and long-term. Key advice includes taking small incremental steps, always leaving code cleaner than found, and justifying refactoring to managers through economic arguments (faster feature delivery, fewer bugs) rather than code quality ideals. For large refactors, he recommends setting a long-term goal and incrementally working toward it rather than scheduling dedicated refactoring sprints.
Sort: