stop refactoring

The term "refactoring" was made trendy a while ago by Martin Fowler, et al. Given that programmers are not generally fans of marketing, it surprises me that what is effectively a marketing euphemism for "rewriting" has become so popular. I think it's time to go back to the olden days, when people called refactoring what it is: rewriting.

refactor later

There's a saying in chess, "When you see a good move, look for a better one."

I've found this applies to programming too. Too many times, I've seen something I didn't like in code and rushed to rewrite it. The outcome, very much like when I rush a move in chess, rarely comes out as well as I'd hoped.

So, when you see something that could be refactored, refactor it later. By then, you're certain to have improved in several ways your plans to rewrite.