3 ms·
"When it does, at a completely uncontrolled time with countless business processes dependent on it, the cost will be HUGE" Couldn't that happen with any app, e
by Tichy 17y ago
"When it does, at a completely uncontrolled time with countless business processes dependent on it, the cost will be HUGE"
Couldn't that happen with any app, even the new ones? I don't quite get the "risk of legacy" debate. Sure it would be nice to get rid of legacy stuff, but should it always be priority 1? I rather doubt it, especially since new stuff becomes legacy very quickly, too. You'd end up wasting all your resources just trying to keep up with the latest developments.
- skolor 17y agoThe risk of legacy is fairly simple: when your brand new app crashes, you have most of the team there, ready to fix it. When your 10 year old legacy app has a catastrophic failure, you have a maintenance programmer, one of a long line of maintenance programmers who all added their own code to it. Basically, the older an app is, the less any person knows about it and the more convoluted it has become.
- billswift 17y agoAnd the more likely you are to have trouble porting it in one jump from ancient to new hardware.