by careinke » Mon 08 Sep 2025, 18:14:00
$this->bbcode_second_pass_quote('AgentR11', 'I') recall fixing stuff for Y2K issues, also had a little stash of cash in case the terminals all didn't work right. But everything turned out fine. Y2K was a real issue, its just that we worked really hard to fix it before it became a problem. There's actually another one coming up... Year 2038 has some interesting surprises in store I bet; won't end civilization, but I bet more than a couple hickups will get noticed. Not my problem though.

Ah yes, Jan 19, 2038 at 03:14:07 UTC, when imbedded 32-bit integer systems will reach their maximum value and overflow, causing the internal clock to reset to DEC 13, 1901. A quick check with my AI, claims there are still millions of products with this problem, including medical equipment.
I was a contractor in Saudi during Y2K, and the problem was taken very seriously, my IT folks were extremely busy. My Sister in Law, with a mathematics degree, (Pre Computer Science Degrees), was heavily involved in Y2K for the Seattle Times. We still have a case or two of Y2K coffee cups, thanks to the Seattle Times. Finally our DINC college friends working at Intel, spent a lot of time trying to break everything Intel owned. NUMEROUS failures occurred at Intel, to the point, our friends were unsure if the deadline would be met.
Bottom line, LOTS of people worked VERY HARD to make Y2K a non event. They succeeded and their efforts should be applauded, not mocked.
Meanwhile, our local parrot, who did not even have Internet, is congratulating himself because he was smart enough to attempt saving a clock. Which apparently was not even needed.
Peace