This document discusses taking "baby steps" when refactoring code. It recommends breaking refactoring work into small, frequent commits in order to make the process more manageable and reduce the risk of breaking the code. Specific tips include automating refactoring tasks using IDE features, committing code every 3-4 minutes, and practicing refactoring regularly in order to improve skills. Links are provided to resources on proximal goals, refactoring best practices, and an upcoming code refactoring workshop.
29. „If you are doing refactoring
your system should
not be broken for more than
a few minutes at a time“
http://martinfowler.com/bliki/RefactoringMalapropism.html
30. „large commits are anti-social“
53 minutes
a commit every 3:30min
15 commits
31. g e t i n t o t h e
MIND
SET@WolframKriesing, uxebu