When I talk about refactoring, I’m often asked about how…
““When I talk about refactoring, I’m often asked about how it should be scheduled. Should we allocate two weeks every couple of months to refactoring? In almost all cases, I’m opposed to setting aside time for refactoring. In my view refactoring is not an activity you set aside time to do. Refactoring is something you do all the time in little bursts. You don’t decide to refactor, you refactor because you want to do something else, and refactoring helps you do that other thing.””
About This Quote
This interpretation was drafted with AI assistance. It is one reading of the quote, not the author's own explanation.
Refactoring should be integrated continuously, not isolated in scheduled blocks; it occurs naturally while developing features.
In simple terms: Do refactoring continuously while coding.
Key Takeaway
Embed refactoring in daily work.
Themes
software development
continuous improvement
code quality
Mood
pragmatic
reflective
Type
advice
process
When to use this quote
- feature development
- bug fixing
- code reviews
- pair programming
Key Concepts
technical debt
incremental change
agile practices
Questions to Reflect On
- How can teams ensure refactoring happens without dedicated time?
- What habits promote spontaneous refactoring?
A Different Perspective
Refactoring may be overlooked if not explicitly tracked.