RefactorbationFiled Under Thought Stuff
re·fac·tor·ba·tion – [re-fak-ter-bey-shuhn]
- To stimulate oneself through endless refactoring exercises towards unattainable perfection
Like everyone young and dumb, there was a time I would refactorbate all the time. The majority of the time I would refactorbate at night, but occasionally in the morning as well. I knew at some level it was healthy, but at the rate I was going I was sure to grow hair on my keyboard.
Now I am older and wiser. I know how to better architect solutions, and I know when to quit refactoring and ship. Sometimes I still do…just for fun…when no one is looking.
But I am very surprised when I watch some of my peers brag about refactorbating. I wince at comments such as “I put 9 overloads on that method just in case someone ever needed them…”. Gross, keep it at home.
That is why I was happy to see this quote from a post called Perfection: Necessary Act
The real trick is in knowing the difference between an act of perfection and an act of codesterbation. When you stop making things better for either solubility, expressiveness, or testability, and you’re still refactoring, you might be in the weeds. – Scott Belware
If you are refactoring to solve problems you don’t yet have, you are refactorbating. Knock it off, your mother might be crying somewhere.