That's a really good principle to work by.
Refactor only if:
I think you should fix it, not refactor if it has bugs. By definition, refactoring does not change behavior.
True, but when we encounter bugs, don't we ask what caused the bug? Too many moving parts? Unclear data-flow? In the postmortem of a bug-fix, the topic of refactoring doesn't come up?
Well said Ezell, I agree that refactoring during a bugfix rewrite is a good idea for sure!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
That's a really good principle to work by.
Refactor only if:
I think you should fix it, not refactor if it has bugs.
By definition, refactoring does not change behavior.
True, but when we encounter bugs, don't we ask what caused the bug? Too many moving parts? Unclear data-flow? In the postmortem of a bug-fix, the topic of refactoring doesn't come up?
Well said Ezell, I agree that refactoring during a bugfix rewrite is a good idea for sure!