Hi Cheeky Kid,
Actually, it's the current range of likely scenarios that are sobering. You don't want to hear the worst case scenarios.
Your analogies are weak. Many people own radon detectors. Radon is a true health threat in certain areas of the country. This is a well-documented fact. Fiberglass replaced asbestos. Unless you stick your face in fiberglass 24 hours a day, there is no know health risk.
I don't know what part of the country you live in, maybe you live in the lower sunbelt, like Eski. But where I live, if you are wrong, and there are power disruptions due to Y2k, I and those around me will suffer greatly. I HAVE to consider the likely scenarios. It's the responsible thing to do. I have seen enough unremediated date logic in my professional capacity to consider the veracity of at least some of the milder Y2k scenarios. If it all gets fixed, great. However, I have my doubts that the same brain-dead managers that put us in this pickle in the first place will suddenly snap-to and pull us out.
The code doesn't know what we think, or believe, or wish will happen. The code doesn't "know" anything. It only does what it has been told to do, and it does it fast. If the date is actually 01/01/2000, but the code has been told it's year 00, and it has been told to extrapolate the century as 19, it will do exactly what it has been told to do on 01/01/1900. It will purge files, it will perform calculations, it will take devices off-line for maintenance, it will start long overdue processes, it will write additional records, it will update existing ones, it will sort the results, and it will encounter negative values for the first time in logic that was written with the expectation that a negative value would never occur.
I hope you are correct. Good luck. |
