>>>This problem — relying on older or deficient software that needs updating — is known as incurring “technical debt,” meaning there is a gap between what the software needs to be and what it is. While aging code is a common cause of technical debt in older companies — such as with airlines which started automating early — it can also be found in newer systems, because software can be written in a rapid and shoddy way, rather than in a more resilient manner that makes it more dependable and easier to fix or expand. As you might expect, the former is cheaper and quicker.>>>
>
>The idea of "technical debt" is intriguing isn't it?

Seen it happen, and seen it be repaid, and it was worth it. Mostly, it's the data crunching and munching that's usually lagging, the database not being properly normalized to start with, that kind of thing. The sooner you clean it up and replace it with a stable, resilient model, which always lands on its feet like a cat, the longer you'll live in that happy ever after.

Begins when you understand the wisdom of „there's never enough time to do it right, but there's always time to do it twice“, and apply that wisdom.