Definitely true. And I think, in retrospect, that's not so bad. I think the important part is realizing - and convincing people to allocate time to it - when

Definitely true. And I think, in retrospect, that's not so bad. I think the important part is realizing - and convincing people to allocate time to it - when it needs to be refactored: when it reaches a point that it can't sustain itself and doesn't solve business problems anymore. Until then, if it's solving a business need and you're not pouring tons of effort/money into it, it's more about pride than a real problem. That is a lesson I had to learn the hard way, and still struggle with: accepting that sometimes a janky, hobbled-together solution that solves a business problem still solves that problem and might not be worth the cost of "fixing."