SoylentNews is people
SoylentNews
As we head into 2015, it's hard to think of any technical skill set less relevant than Y2K - the identification and fixing of computer systems and applications that used two decimal digits rather than four to store the year component of each date. As you may recall, the discovery of the problem (or perhaps, that the deadline to fix it was finally approaching) in the late '90s led to media hysteria and dire warnings about a world full of computers simultaneously losing their bearings, like HAL in the film 2001: A Space Odyssey. An artist has assembled a memorial to the crisis, in the form of a web site presenting photos of dozens of books dealing with Y2K from various perspectives.
This site could be seen as mindless diversion, but also as a digest of reaction likely to repeat itself in a subsequent "crisis", albeit with different media next time (blogging, for one, had yet to be invented).
(Score: 1) by Nuke on Sunday January 04 2015, @04:59PM
No doubt banks and corporates did fixes but I'm sure that no ordinary person in my circle bothered, nor did I. There must have been thousands of small businesses that did not bother either, or had no clue what to do.
Yet I heard that the only Y2K failure across the world was that the one-armed bandits at a Nevada race course stopped working. An apocryphal rumour no doubt.
(Score: 0) by Anonymous Coward on Sunday January 04 2015, @05:38PM
If you google for "list of y2k failures" [google.com] there are a bunch of sites with a bunch of different lists of failures. Just because airplanes didn't fall out of the sky doesn't mean glitches weren't widespread.
(Score: 3, Informative) by black6host on Sunday January 04 2015, @06:41PM
Indeed, most all of our applications were developed in house, in Clipper. I found many points of failures that would trigger if nothing was done.
The biggest challenge was getting the President to understand this stuff had to be fixed. So we did, took a while but no failures once the code was changed. It was a good opportunity to clean the code a bit as the original programmer liked copy/paste and had little concept of re-useable code in the form of functions, etc.
Of course, when the big day came, everything worked like it should have. So everyone was saying, "See, that was no big deal". Well, no, it wasn't. Because we busted our ass to fix things.
I still hear that it was no big deal from time to time. But never by anyone who was responsible for setting things straight before they became a problem.
(Score: 1, Informative) by Anonymous Coward on Monday January 05 2015, @06:47AM
If they updated their Windows they did and if they ran *nix they didn't have to: Y2K was not about personal computers and thus normal people are entirely clueless. Y2K was about ICs, embedded computers, ladder programming, industrial systems, all kinds of infrastructure including financial and military, electrical substations, water management, dams, power generation and redundancy, heavy and dangerous industry like steel plants, chemical plants, oil rigs, refineries etc.. Yes you had the COBOL brigades too.
Replacement components had to be tested both before and after installation to the extent possible before turning on the entire systems. Sometimes there were no alternatives to complete shutdowns but one really wants to avoid shutting down plants that take months to stop and start so a lot of it was figuring out the planning of how to do simple things in very difficult contexts. Sometimes what was supposed to be working replacements still did not work correctly together with other components despite all kinds of certified guarantees and you don't want to discover that after a chemical plant wipes out a small village or city.
We all got a little bit lucky as well: ladder programming could have been a much bigger issue or downright nasty but as far as I know it held up fairly well, same can be said for the higher libraries. There are a lot of people to thank for this over many decades, many of them dead and gone long before Y2K.
Y2K was hairy, one barely got the most critical items done before the date and what wasn't ready had to be shut down. The work continued on at a lower but still high pace for six more months. For even less essential stuff short-term pivoting became the solution; that's what most ordinary companies and government departments ended up doing and maybe some of them still are.
Essential people worked themselves into ill health. I wonder how many died during the latter half of 2000 from the stress they had been under, it would be surprising if no one did. Nearly everyone I know about quit during 2000, a lot of them had postponed retirement or been dragged back out from it, this was their last job.