Honestly, yes. Code is a liability, not an asset. Over time it decreases in value, it is forgotten, misunderstood, and everything will change around it. Many

Honestly, yes. Code is a liability, not an asset. Over time it decreases in value, it is forgotten, misunderstood, and everything will change around it. Many times I've been happy to replace a custom system with an off the shelf one, just to reduce the amount of code I have to worry about. Even if you keep working on it, requirements change, the code becomes a tangled mess and requires refactoring, tests need to be more complicated, you have to support more operating systems, etc. At best it does what it needs to do well enough to pay for itself, and then some. Until it needs more work! You don't realize it's crap until it goes wrong and you look under the hood usually either.