Oakthicket wrote:In the end, there wasn't a single significant Y2K problem anywhere in the world. This includes countries that did nothing to address Y2K 'issues'. The idiocy of the masses was never widely discussed. The subject disappeared quickly.
The reason the Y2K computer bug didn't result in widespread problems was that programmers worked hard, and successfully, to solve the problem in advance.
Despite this, when I was working for U.S. Sprint, it was reported internally that one of the Sprint call centers went down promptly at midnight as the clock ticked over from 1999 to 2000. Admittedly it was only out for a few hours, but to pretend the problem didn't exist is absurd.
Complete and utter bullshit. You've joined the fringe woo-woo crowd on this one Lens. Show me one power plant that went down, one elevator that got stuck, one flight that crashed, one anything of significance.
My company spent $40 million and found absolutely nothing.
The Y2K outcome isn't a matter of opinion, speculation or uncertainty. It's a matter of public record. There were numerous countries that did nothing. There were numerous corporations that did nothing. Nothing happened.
I'll save you the trouble of looking up Wiki on Y2K problems on January 1, 2000. Here they are.
* In Sheffield, United Kingdom, incorrect Down's syndrome test results were sent to 154 pregnant women and two abortions were carried out as a direct result of a Y2K bug. Four Down's syndrome babies were also born to mothers who had been told they were in the low-risk group.
* In Ishikawa, Japan, radiation-monitoring equipment failed at midnight; however, officials stated there was no risk to the public.
* In Onagawa, Japan, an alarm sounded at a nuclear power plant at two minutes after midnight.
* In Japan, at two minutes past midnight, Osaka Media Port, a telecommunications carrier, found errors in the date management part of the company's network. The problem was fixed by 02:43 and no services were disrupted.
* In Japan, NTT Mobile Communications Network (NTT DoCoMo), Japan's largest cellular operator, reported on 1 January 2000, that some models of mobile telephones were deleting new messages received, rather than the older messages, as the memory filled up.
* In Australia, bus-ticket-validation machines in two states failed to operate.
* In the United States, 150 slot machines at race tracks in Delaware stopped working.
* In the United States, the U.S. Naval Observatory, which runs the master clock that keeps the country's official time, gave the date on its website as Jan. 1, 19100.
* In France, the national weather forecasting service, Meteo France, said a Y2K bug made the date on a webpage show a map with Saturday's weather forecast as "01/01/19100". This also occurred on other websites, including att.net, at the time a general-purpose portal site primarily for AT&T Worldnet customers in the United States.
With the exception of the Sheffield, England incident, none of the other events would normally warrant media attention. The types of Y2K issues reported happen all the time for different reasons. That includes the Sheffield incident.
Although there are no firm numbers, estimates of worldwide Y2K expenses are in the $300 - $500 billion range. I'm sure many folks appreciated getting new computers and system upgrades because of Y2K paranoia.
Your comment about programmers working hard, therefore avoiding Y2K issues is the same as superstitious tribes sacrificing someone every day before dawn to ensure that the sun comes up. When the sun rises, it reinforces their beliefs that human sacrifice was necessary.
As with many things the actual answer is somewhere in between these extremes. I was a regional CIO for Lockheed Martin during the run-up to Y2K and was responsible for many millions of lines of legacy applications code that needed to be remediated for Y2K rediness.
Our remediation projects were substantial in scope and there is no doubt that there were some real issues that would have caused real problems with substantial financiatial and operational consequences had nothing been done. And yes, a lot of programmer/analysts worked hard to avoid these issues. The fixes however were very straight forward so it was merely a matter of finding all the issues, making the code changes and testing them for Y2K compliance (the testing was actually one of the more difficult parts). In LM, I do not recall any major Y2K caused outages/losses.
That being said, I think I can speak for most of my peers at the time (with whom I attended endless conferences, etc. that were held on the subject) that the whole Y2K threat was totally overblown by non-computer literate management who a non-computer literate press had in a non-computer literate tizzy over the whole business which was really just another (among many) legacy applications issue to be resolved. The amount of time money and worry afforded to Y2K issues was absolutely ridiculous IMO.