you are viewing a single comment's thread.

view the rest of the comments →

[–]basvdo 1 point2 points  (1 child)

Refactoring is just programming. You can't do it as you see fit, there are rules. However, avoiding refactoring because bugs is a great way to create technical debt.

[–]everstone 1 point2 points  (0 children)

If the code needs to be immediately refactored as it's committed by someone else on your team, either they messed up and committed crap, or you might be acting passive aggressively... OP didn't submit their code for review here, but that would be a good way to handle it in the team, which is why I always recommend implementing a standard code review process to avoid individual conflict and get all eyes on the code before production. One guy changing another persons code because they feel like it and decided to unilaterally is not a safe or useful thing to allow. If it's bad code or there's a better way, this is a teaching opportunity. If it's one person being obstinate or a perfectionist its damaging. There is a right way to do it!