I not arguing is effort-free, but is effort-minimal. The idea allows, at most, one or two major steps, the first and the biggest is as simple as is possible and

I not arguing is effort-free, but is effort-minimal. The idea allows, at most, one or two major steps, the first and the biggest is as simple as is possible and can be done in one go, and have zero possibility of breaking. The only major issues is that the change is let half-way. But that is only possible with MAJOR undisicpline. --- The major point, to me, is that this EXCESSIVE fear of breakage is not good. Yes, making upgrades is pain, but you CAN make the pain tolerable with some planning. Refactoring is like exercise for code: Everyone dislike the idea of excessive, but is GOOD. And lets be honest, among all the things that could requiere a refactoring, this case is on the most simples of the simples scenario..