Oh, there were hiccups for sure - plenty of issues that weren't caught until the real thing happened. But fortunately, the due diligence headed off most of the serious impact. :D
Top-level
Oh, there were hiccups for sure - plenty of issues that weren't caught until the real thing happened. But fortunately, the due diligence headed off most of the serious impact. :D 8 comments
@tychotithonus @ljohn44 @Xavier @robertatcara A lot of mom & pop businesses relying on ancient equipment for payroll, inventory, orders, etc., had failures but they didn't advertise that fact. @Lizzz @tychotithonus @ljohn44 @Xavier @robertatcara at the micro scale delete and setup fresh in Jan was a workable solution. It's an annoying arvo for someone. It's the big businesses that needed to act, and by and large they did. @ysegrim @Lizzz @tychotithonus @ljohn44 @Xavier @robertatcara Yes, a lot of work was done to prevent problems. And, in the weeks following, a lot of work was done to detect, prevent, and recover from problems. ACM's "comp.risks" usenet forum describes some of the problems that happened. Interesting! I haven't read them in detail, but here are some convenience links to the Usenet comp.risks posts for the month of January, 2000: https://groups.google.com/g/comp.risks/c/7AGzwqmZtH8 Briefly, from memory, there were *quite a few* problems of small retail establishments resending duplicate charges due to bugs in their software that treated "year 00" as something that could never happen. This would have been avoided by updating their software. And they were informed. Problems were averted by banks detecting and rejecting the duplicates. Also, we lost track of one of our spy satellites for a few weeks. Read the comp.risks entries for details. @ysegrim @tychotithonus @ljohn44 @Xavier @robertatcara Interesting that being in different TZs would have given all of us different experiences. |
@tychotithonus @Xavier @robertatcara As a regular person just going through life it appeared seamless. Thank you!