Quote:
Originally Posted by zcaveman
Never considered the time spent on Y2K stuff wasted. Thanks to the extreme efforts by IT and programming areas everywhere, Y2K went off without a hitch. We were the reason that they labeled it a big do nothing scare or the Y2K hoax. If we had not done our jobs there would have been a LOT of problems.
I know because I tested before and after applications and worked with numerous vendors to get their products fixed.
Anyway so as to not hijack the thread, Twenty-Ten seems to work.
|
Hi neighbor,
As you said, this is a hijack, but, as you are an expert, I can't help asking your more about Y2K. I thought it was a hoaks too, for a few reasons:
- In my unknowledgeable "logic," I thought code was just a bunch of "1"s and "0"s to a computer. I didn't think computers knew or cared wether one number (1999) was higher or lower than another number (2000).
- I couldn't understand why a computer would be be confused about 2000 following 1999, but not 20 following 19.
- As I recall, April x, 2000 (I forget the exact date) something also was supposed to happen because the digits for that date meant something else somewhere else in the computer code. But I couldn't understand how one line of code governed by one set of coded paramerters would confuse another line of code governed by a different set of coded perameters.
- Convinced there was nothing to it, I did nothing to my home computer, nothing to my digital clocks and nothing to my appliances that had digital clocks. I didn't even change the date display on my home PC to show the 4 digit vs. 2 digit year. Come Jan. 1, 2000 all my home stuff worked the same as it had on Dec. 31, 1999 and before. Excel '97 (I think?) worked flawlessly, although I did not upgrade or run any program to correct it. Quicken '98 worked flawlessly, although I bravely and defiantly didn't upgrade or run any program to correct it. (Ok, not that brave and defiant-- I always backed it up.) Outlook, Word, and all my other non-y2k compliant programs worked flawlessly
- Whatever that date was in April-- I think there was one in February too?-- that something was supposed to happen to my non-y2k compliant hardware, again, nothing did.
So, zcaveman, any explanation you can provide demonstrating it wasn't a hoax, I would like. I realize I don't know what I don't know, and I enjoy trying to expand what I do know. Thanks.