4 ms·
Working Effectively with Legacy Code recommends just this idea. They call it scratch refactoring. Refactor without a lot of forethought to see how the system wo
by chucksmash 8y ago
Working Effectively with Legacy Code recommends just this idea. They call it scratch refactoring. Refactor without a lot of forethought to see how the system works, then just throw away your changes but keep your newfound understanding.
- lugg 8y agoThis is effectively "it." But I do like to branch off the more useful refactors into their own commits.