Who remembers the hysteria about the Y2K bug ?

misterski

Well-known member
Everyone remembers the hysteria, but many don't know about all the work that went on behind-the-scenes to prepare for it. And that behind-the-scenes work paid off with a mostly good result. There were still some failures but not the widespread system crash that everyone feared.
 

LokiFrost

Qui Tacet Consentit #RESIST
Who remembers the hysteria about the Y2K bug ?

// The cost to fix the Y2K bug is estimated to have been between $300 billion and $600 billion globally, with the United States alone spending around $100 billion. //

ChatGPT is your friend :)(y)
I loved the Y2K bug (and the anxiety it caused local, state and federal agencies).

Between mid 1999 and end of Q1 2000, my income jumped from 30K to 80K.
I used the extra money to put myself through school.

~Loki
 

Eoin-1

...once the Symphony of the Fey event is over.
Still dealing with Y2K issues at my work. We keep sliding the sliding year window. Drivers and vehicles aren't unaliving within 90 years, which makes for some interesting issues.
 

Rusty_helmet

Teh_troll’s Fluffer
I was on a plane over Y2K and the computer failed and we had to land old school. It was not a Y2K related failure, but people were pretty scared.
 

svenofnein

Well-known member
I remember waking up 1/1/2000 and thinking, 'ah, that's a shame'. But I teeter between chaotic neutral and chaotic evil.
 

TrinityTurtle

Forum Turtle
It was never a hysteria.
A lot of money and resources was spent to make sure nothing bad happened before the century turned. That is why nothing happened.
I sometimes feel like people are allergic to planning ahead. Recognizing there is a flaw and spreading the information and making plans to prevent the flaw from becoming a Problem is a good thing, not hysteria.
 

LokiFrost

Qui Tacet Consentit #RESIST
It was never a hysteria.
A lot of money and resources was spent to make sure nothing bad happened before the century turned. That is why nothing happened.
There were a lot of bad things that happened during and after Y2K, the general public doesn't remember or didn't care because the world didn't end and it didn't necessarily impact them, per se.

Some of the biggest things that I personally helped resolve was in Lake City, FL.:​
  • They had several county and federal jails/detention centers whose automated cell locking systems opened up the doors at random times throughout the night; this included the ingress and egress doors to the facilities themselves. We had to sift through 50K lines of code that was cobbled together from COBOL, FORTRAN and LISP to help resolve these issues.
  • Additionally, they had a regional airport that experienced random shutdowns and reboots of command and control systems, including RADAR and FAA connectivity. My company helped resolve those issues as well.

On a larger scale was the Y2K work we did for the federal government:​
  • One of the more "fun" things we helped fix was Lotus123 for the federal govt. At the time, US Customs had Lotus123 integrated into every aspect of their systems at the old datacenter in VA. This was a nightmare to resolve because of the integration with Novell integration issues.
  • For a brief time, US Customs servers and network appliances actually stopped talking to other agency systems.
  • My company tried to resolve all these bugs with Lotus123 and in the end, migrated them to Domino and Windows-based servers (NT).


None of this stuff made the news and yet, in my book, were "bad".

~Loki
 
Last edited:

Sarlona Raiding

Well-known member
  • One of the more "fun" things we helped fix was Lotus123 for the federal govt.

~Loki

Heh the first project I worked on out of college was converting 123 spreadsheet calculations put together by non-IT experts into c++ code.

The y2k problem wasn't hysteria, but without a doubt IT departments and software engineers used the situation to get way more budget $ than they needed.

The reason it went so smoothly is because most organizations prepared and mitigated properly.

The US Bridge system is an example of something that we didn't prepare for and mitigate properly.
 

Arkandor

Member
As the weirdo who privately owned a computer, I was tasked with that y2k stuff in our department, nothing world-breaking but some documentation would go awry if there actually were any production in the night of dec 31 (like the heat-treatment after certain production processes missing the 3h deadline, or the sudden realisation that that unique part number used in 1999 was already used back in 1970.)

But yeah, there was a lot of angst back then, and it was frustrating, trying to convince folks in their 50's that very little will happen.
Well, now I'm in my 50's and Y2K38 will be our doom, I tell you!
 

LokiFrost

Qui Tacet Consentit #RESIST
One of my first jobs out of school was writing firmware (C##, Assembly, etc) for HP and Compaq. 10BT network cards, BIOS, routers and printers.
Good old days!

~Loki
 

LokiFrost

Qui Tacet Consentit #RESIST
As the weirdo who privately owned a computer, I was tasked with that y2k stuff in our department, nothing world-breaking but some documentation would go awry if there actually were any production in the night of dec 31 (like the heat-treatment after certain production processes missing the 3h deadline, or the sudden realisation that that unique part number used in 1999 was already used back in 1970.)

But yeah, there was a lot of angst back then, and it was frustrating, as an 18 years old trying to convince folks in their 50's that very little will happen.
Well, now I'm in my 50's and Y2K38 will be our doom, I tell you!
DOOOOOOOM
 

misterski

Well-known member
As the weirdo who privately owned a computer, I was tasked with that y2k stuff in our department, nothing world-breaking but some documentation would go awry if there actually were any production in the night of dec 31 (like the heat-treatment after certain production processes missing the 3h deadline, or the sudden realisation that that unique part number used in 1999 was already used back in 1970.)

But yeah, there was a lot of angst back then, and it was frustrating, as an 18 years old trying to convince folks in their 50's that very little will happen.
Well, now I'm in my 50's and Y2K38 will be our doom, I tell you!

Ahhhhhhhhhhh!!1!!1!1111!!!!!!! The UNIX EPOCH DISASTER!!!!1!11!!1!!! AHHHHHHHHHHHHHHHHH!1!!!1!!1!111!!!!1!!1!!!!1!!!!!!!!!!!!!!

Edit: Added 1s to the exclamations to clarify how scary this will be
 

LokiFrost

Qui Tacet Consentit #RESIST
Ahhhhhhhhhhh!!1!!1!1111!!!!!!! The UNIX EPOCH DISASTER!!!!1!11!!1!!! AHHHHHHHHHHHHHHHHH!1!!!1!!1!111!!!!1!!1!!!!1!!!!!!!!!!!!!!

Edit: Added 1s to the exclamations to clarify how scary this will be
I miss sharing processor time on my old mainframes. :cry:
Or having to send print jobs to the queue for 4 am printing; hoping that I didn't make a mistake and print out a ten thousand page report instead of a 10 page report...but having to wait until the next business day to find out.

My stress levels were much more manageable back then. :ROFLMAO:

~Loki
 
Top