Right, Rand. Let me give you another example: You have a reporting system that works, however, it will take bloody ages to generate its report which is why its done as a batch job overnight.
New algorithms, new databases, new hardware comes around and with an upgrade you now might obtain your reports in near-realtime.
But, since the old system works, you forgo the upgrade.
That's good business sense right there, hmmh? Geeze, even the aerospace industry is less conservative than you.
You obviously don't know what "bleeding edge" is. Anything newer than what you're using is "bleeding edge"? What idiotic definition is that supposed to be? Good lord, let someone like you never be in charge of IT.
I can only imagine it: You're upgrading from old 286 with Windows 3.11 to Pentium 2 with Windows 98 - and you'll call that "bleeding edge".
That'a actually not a point for your argument and you know it.
Wait, I thought your system was so reliable that it never failed?
Not to mention that I'd be somewhat suspicious of the reliability of a system if someone told me that "people know instinctively what to do". Because that means to me that faults happen so often that people have it fully memorized. Or that the faults are so trivial that a trained monkey could do the right thing.



Reply With Quote