"But code that is riddled with defects is a cameleon - one moment it works, the next it doesn't anymore. That leads to fear of refactoring, which leads to spagh

"But code that is riddled with defects is a cameleon - one moment it works, the next it doesn't anymore. That leads to fear of refactoring, which leads to spaghetti code" - I couldn't agree more. We just had a new feature request come in last week, which I had to implement. 20% of my time has been devoted to writing the module and 80% of my time has been devoted to integrating it with legacy code. With each successive iteration it's taking longer to develop features then it did before, all because of the "pick two" agenda