I don't know that it's possible to prevent it, but include the coder's perspective in a team conversations about the project, standards and such If it's innocu

I don't know that it's possible to prevent it, but include the coder's perspective in a team conversations about the project, standards and such If it's innocuous and they have a bee in their bonnet, consider letting them refactor on their own branch, and subject it to normal code review Recount the Parable of Chesterton's Fence Ask them if they are just bikeshedding Let them make low cost mistakes to learn cheap lessons, saving expensive lessons later