3 ms·
If it works, has all necessary features, no significant bugs, and still performing all functions - why change? Especially since the change to modern technologie
by xvilka 6y ago
If it works, has all necessary features, no significant bugs, and still performing all functions - why change? Especially since the change to modern technologies will not guarantee to produce a better result in terms of features and stability. The change is necessary if the system unmaintainable, buggy, or can't be easily interfaced with other modern systems.
- shakna 6y ago> The change is necessary if the system unmaintainable, buggy, or can't be easily interfaced with other modern systems. Unfortunately, all of these are frequently true of legacy systems. Only a small number are relatively bug free. Most are simply unmaintained. Few are easy to interface with. I have no particular problem with old software and hardware. But the massive expenditure leading up to Y2K is demonstrative of the legacy problem. Let it rot until an impending crisis forces your hand, costing far more than if you had simply maintained it.
- oblio 6y agoUnless you want to end up with Adeptus Mechanicus worshipping the Machine God in the MS-DOs boxen, you need to change from time to time. You need to at least be able to open the metaphorical box and see if you can reproduce it in case of disaster recovery. The more important the system, the higher the existential threat for the organization if you just let it be. I do understand that it's a thankless job, so this needs to be enforced from up high.