Does having a strict code review process prevent or discourage refactoring?
If I want to make a very small refactor, like renaming a variable, am I likely to do that if I need to make a feature branch, create a merge request, and wait for multiple reviews from team members?
What if it takes a day or more for someone to review it?
Is it worth a reviewer's time to review a refactoring that could only be a single line of changed code?
Alternatively, what if you were doing trunk-based development and/or continuous integration?
What if you could make the small change, push it and have a CI pipeline automatically review it?
The whole process could be completed in minutes.
Nolong wait for manual code review and once you finish that refactoring, [you may find another](/daily/2025/06/13/refactorings-should-be-small).
format:markdown
processed:|
<p>Does having a strict code review process prevent or discourage refactoring?</p>
<p>If I want to make a very small refactor, like renaming a variable, am I likely to do that if I need to make a feature branch, create a merge request, and wait for multiple reviews from team members?</p>
<p>What if it takes a day or more for someone to review it?</p>
<p>Is it worth a reviewer's time to review a refactoring that could only be a single line of changed code?</p>
<p>Alternatively, what if you were doing trunk-based development and/or continuous integration?</p>
<p>What if you could make the small change, push it and have a CI pipeline automatically review it?</p>
<p>The whole process could be completed in minutes.</p>
<p>No long wait for manual code review and once you finish that refactoring, <a href="/daily/2025/06/13/refactorings-should-be-small">you may find another</a>.</p>