Post

Because it's come up recently, a reminder that the Y2K bug wasn't overhyped. It was a huge problem and an huge number of people worked fast and hard and fixed it. Like the ozone hole. It's not a lesson in overhype. It's a lesson in humankind's ability to cooperatively solve problems.

593 reposts2.2K likes

Curious thing is, you almost never see articles addressing possibility that the reason we didn’t see major disruption or catastrophic events was because a lot of skilled human effort went into fixing the issue….

My dad was actively involved in Y2K-mitigation strategies at the time. I remember him saying something to the effect of "we worked hard to fix something so that you wouldn't notice a thing". And indeed I didn't. I was too engrossed in playing first-gen Pokémon to notice my PC didn't crash, lmao.

Our computer classes had projects to test and apply all kinds of y2k patches across the school the 2 years before y2k. A ridiculous number of things had to be patched, including the scantron hardware and software they used for attendance and testing. We missed a photocopier and it stopped

deducting copies from the copy codes entered because the usage happened in 1900, outside the current allotment. It took until most teachers knew about the issue 2yrs later and used a year’s worth of paper and toner in 2 months.

A similar thing impacted telcos with their switches. I found several while I worked at the phone company. One in 2015 was a busy long distance switch that wasn’t reporting the right dates to the billing system, as a result 15yrs of LD calls through that switch went unbilled.

I've met people who think it was a hoax largely because they were unaware of the Y2K compliance industry. I think 98-99 is better described as "mass hysteria." People just said whatever they wanted and that overwhelmed anything about audits and insurance that happened years before.

I was in the middle of that remediation… nuts is a good word for it. What terrified us wasn’t what we knew about. It was what weird Assembler or COBOL was lurking in some disused basement of the Main Frame that was going to rise up on that day and kill the Bank

By the time Y2K rolled over we knew we had the critical stuff mostly fixed. We had worked over 3 years on fixing and replacing most of our systems. There was always the possibility that some critical machine somewhere might have been missed, but we were pretty sure nothing bad would happen.

I worked for a telco and found a ton of unpatched switches over the years. Last one I remember was a busy long distance switch in 2015 that wasn’t reporting calls to the billing systems because of the date. 15yrs of operating at/near capacity and nobody was billed for all those calls.

I remember around the time of y2k we discovered that all our Cisco switches had a hardcoded default passwords in the firmware. Put there by Cisco and we had to get firmware upgrades and/or new routers. Our network guys were not impressed. Never got hacked that we knew of. 🫤

People also forget it wasn't just 1999-12-31, I was working for the IT department of an internationally well know department store and an a customer tried to pay with a new credit card that had an expiry date of Jan 2000, it was rejected by the validation system. This was in 1995.

Most people have no idea of the work that went on in 1999 to avert a disaster. Retirees were brought back as they knew the ancient computer languages that many systems ran on which had to be reprogrammed.

After many thousands of man days, we changed all our systems successfully for Y2K. All db had Januark, Februark, Mak, Julk+Sundak,Mondak etc. We were very proud! Dunno why we got fired tbh, we delivered exactly what they asked for 🤷‍♂️ (Reality:I was a Y2K coordinator at IBM..lot of hard work)

The Y2K problem was like the It's Always Sunny in Philadelphia ep "Charlie Work". Charlie does loads of crazy stuff to get the bar past its annual health inspection. At the end the gang says it's "not a big deal because they always pass it", giving no recognition to work done by Charlie to pass it

The media and non-professionals did overhype it, though. A lot of work was done to fix potential issues, and there could have been major problems, but there were people saying that some things might happen that were totally unlikely.

And they continued to spout the fear-mongering even after the problems were mostly resolved, right up until the new year was starting. It was a very serious, very big deal, that got resolved, and yet was still over hyped at the same time somehow. @_@

My father has worked in tech his whole career. As 1999 was ending, I finally asked him if it was as big of a deal or worth the stress that I was seeing in the news. His answer was: "It's already fixed." It was a problem, but the professionals handled it like professionals, and here we are now.

It'll be far less than Y2K. Unix time is stored as a 64-bit number already and most programs will be using a time/date library to convert Unix time to DD-mm-YYYY (modern libraries will all cope), and database management systems are already 64-bit aware. With 64-bit Unix time there's no problem.

Yes, this is what I was referring to... Generally not a problem as long as we have moved on from 32-bit systems or 32-bit systems which have been patched, and yes, this is typically Unix and Linux systems.

As someone who grew up around tech but not in the industry at the time, this is 100% correct. If not for that hard work, things would have been very different.

Tons of stuff was missed and the problems weren’t immediately apparent. The telco I worked for missed patching a ton of switches. Last one I accidentally found and cut a ticket to fix in 2015 was a busy long distance switch. 15 yrs of calls went unbilled. It ran at or near capacity the whole time

i'm not downplaying the seriousness of it at all, I hope that's not the impression people are getting. And yeah there would have been a ton of little gremlins to stamp out. I just meant compared to the media hype on the topic, the tireless work BTS from everyone to ensure the worst case scenarios/

DIDN'T happen, the reaction from regular people has always been 'that was a lot of fuss over nothing', not realising it's only *because* of the insane amount of work that went into it, that made it seem overblown because nothing major happened. Apparently we took the wrong lessons from it 🥺

In one of the video games I play, "enemy crit chance down" was mathematically one of the strongest abilities because it dramatically improved your team's survivability by making incoming damage consistent. It was a very unpopular ability because players never noticed its impact - you dont notice

something NOT happening. The devs had to add a "critical hit avoided" text for people to even start noticing it. And it still wasn't popular! "We spent $10m to renovate this bridge and now it won't collapse" is unpopular because you can't demonstrate the counterfactual!

I accept it was a big potential problem, not helped by some practitioners. My IT Head asked for a big bonus to prevent our systems crashing. I suggested that was what we paid him for, so he should avoid a crash if he wanted to keep his job. He did.

Still confused by Y2K, since you'd think programmers wouldn't be unaware of the upcoming changing of the millennium when they were working in the '80s. How come there was so much work to do, to ready important software for something so basic as the capability to acknowledge dates in the near future?

Imagine working on something, and you know in 2044 it'll trigger a bug, but your boss wants you to work on new feature X right now first. Repeat that a million billion times until it's almost too late. It's like climate change, only we actually *addressed* Y2K before it got bad. 😐

Saving two bytes for every timestamp was important in an era when 128K could be all the memory you have. Moreover, the problem wasn't really widely known about until the internet became big enough to spread the word.

Wouldn't have twigged that last bit. At the same time it seems like "dates run up to [near future]" would be a self-evident problem, unless you saw your work as up for immediate replacement. That's a big question, the idea that no software or hardware is going to be kept around like a good novel is.

I do think "it will get replaced by then" was also a common thought. Tech was improving so rapidly that it seemed silly to expect the system wouldn't be replaced in a decade. Also, 2000 wasn't considered the near future - it was "The Year 2000." Very mystical and far off, until it wasn't.

Or any other creative product. Obv. a computer has more moving parts than a marble statue, but I'd love to hear the deep dive on how much tech after a certain point has the potential staying power of the polaroid camera, the solar pocket calculator, the magnetic compass. Idk the software equivalent.

I had an old PC, like 10 years old. I heard the Y2K stuff, so I tested it by copying the files I needed, then set it to December 31 1999, 11.59PM. It simply went on to January 1, 2000, 0.00AM. No one had done any remedial work on it. Then I set it back to the real date & time & forgot about it.

I was just thinking about this re: covid (and pending bird flu). Even though the US response was terrible bc Trump, many systems were in place that helped many of us avoid it. But people say, "It was overblown, no one I knew died." Think how many people's efforts it took for you NOT to die.

I got covid and was the sickest I've ever been, and that was WITH the vaccine. Some people would say "see, the vax doesn't work" but I just dread to imagine how much worse it would have been without.