Post

DAMMIT NPR. I spent nine months upgrading over TEN THOUSAND desktops at a F500 client. The grand total was over SEVENTY THOUSAND applications upgraded. Y2K "didn't live up to the hype" because the industry busted ass to duct tape everything first.

NPR@npr.org

People feared the computer glitch would mean "the end of the world as we know it." Thankfully, Y2K didn't live up to the hype after years and billions of dollars were spent on painstaking preparation.

2.9K reposts14.8K likes

I also remember converting all the year data fields from 2 to 4 digits so date arithmetic would work. I agree, there wasn't a lot of failures, because all the hype alerted everyone ahead of time to take care of it!

"Didn't live up to the hype" isn't how you describe successfully averting disaster. Imagine a news org saying a terrorist attack didn't live up to the hype after police arrested the organizers before they were able to plant the bomb. Would that sound right to you?

You're both making valid points. It should've been worded differently for better tonality AND the article does make the very point the OP is complaining about it ignoring.

He his exactly saying that the context is different from the one painted in the article. Without the so-called "hype", he would have probably passed way more quality time with his family during the holidays (or whatever).. Only for a lot of "woopsies" come up on January 1st.

The hype around Y2K was that microwaves would stop working, and everything else with microchips too. We were told the computer age couldvend. That never happened. And I don't doubt for a second that the tech industry charged a lot of money for very little work.

What do think "the tech industry" was in the 90s, and who do you think they were charging? It actually was a lot of work. Making sure that software wouldn't treat the year 2000 as 1900, 19100, or a memory overrun and making sure you didn't break anything else in the process wasn't easy.

It's extremely common for people to use y2k as an example of people panicking about a thing that ended up being nothing and when someone says it didn't live up to the hype the implictaion is that the money and work spent on it was a waste. It's wasn't hype. It was a real problem.

This was a completely different context. We spent all of 1998 and 1999 wondering if the lights were going to come on in January 1, 2000. Nothing at all similar to a terrorist attack, and a very weak comparison. I'd suggest you listen to a little more NPR to sharpen your critical thinking skills.

I spent many very boring hours at my former company testing all the new coding needed to update our systems for Y2K. It was "nothing" because companies invested the resources to make it "nothing." Had nothing been done, it would have been "something."

I was hired by IBM in 1987 to introduce virtualization to banks in the UK and some in France and Germany so they could start building Y2K testing systems and put the clocks forward on giant mainframe systems. Everyday was 1999 for 12 years.

I was explaining this to my wife. Part of the problem was created by stupid executives forcing workers with nothing to do with IT to work through that night “in case”. She was hr and they insisted she work all night

Sure sounds like the second half of the sentence is acknowledging that: “…and billions of dollars were spent on painstaking preparation.”

I spent one year leading a team of engineers working the issue. In addition to debugging all the y2k problems, we also spent time testing everything. It was the most satisfying project I did as a SW Engineer.

Sigh. Here we go again. Banks tested their systems and they went tits up. They did not spend 10s of millions of dollars for something that would not have caused any harm what so ever. But? You can choose to believe otherwise.

They also, in response to the Die Hard film in which hackers took control of several public utilities, for a tech from the Best Buy geek squad to explain whether or not it was plausible, and it was very obvious that the guy didn't even know what infosec was.

Italy spent almost nothing on proofing computers against the Y2K bug, and yet avoided consequences just as easily as countries like the UK, which spent hundreds of millions. Sadly, the Y2K story is one of media over-reaction, leading to an utter waste of time and money.

Y'all really griping about an article praising your effort? You don't even have to read the full article. It's right there in the headline -- "years and billions of dollars were spent on painstaking preparation". DAMMIT yourself a little.

The implication of “didn’t live up to the hype” isn’t that it was a successfully averted disaster, but that it wasn’t even a big deal, which is unfortunately now the popular conception

Bingo! I worked hard enough and knew plenty of other professionals who worked hard enough to make sure nothing did happen. Y2K was real but professionals did their job to make sure the worst case never happened.

The telecommunications industry started installing software changes in 1995 to handle the date changes. It was all major media hype designed to panic the public, without any understanding of what software companies were doing.

Absolutely. The industry took the issue seriously and put a lot of time/money/work in to addressing the problem. Still, hyperbole was stark. Some doomsaying was likely overblown. Yet that hyperbole was part of motivating companies to fix the problem and avoid cascading failures. A success story.

The sentence can be interpreted to say that all of that was done unnecessarily because nothing happened, not that nothing happened because all that was done. That’s the issue. If you don’t know the work that was done prevented it, then you could believe it was a big overreaction

This same attitude/approach is applicable to manner in which many people evaluate vaccinations which save us from the dire consequences of disease within the population. We are doomed by success, it would seem.

The article says exactly that. “Besides a few minor setbacks like an internet slowdown and reports of malfunctioning clocks, the aggressive planning and recalibration paid off.”

My first project as a PM was Y2K. Upgrading all our servers in our Dara centre and onsite at our clients. It was a huge undertaking by all IT staff across all companies. Still don’t know if it made a difference or not but maybe that’s why we didn’t find out.

People are staggeringly stupid. This is right up there with people’s who think polio is no big deal because the vaccine worked or no one talks about the ozone layer anymore because we fixed that too. Y2K was a very big deal. We fixed it.

At AOL, we spent TWO YEARS fixing and testing shit. We had devs, QA, and admins who were brought in SOLELY to work on it. This is like saying "the hurricane wasn't a big deal" because the city was encased in a hermetically-sealed unbreakable dome.

I had someone on FB absolutely tear me a new asshole because I didn't know this fact. I was also not yet an adult that particular year. Maybe some people don't know some things. I'm sorry the news keeps inaccurately reporting this and perpetuating this misconception, though.

no way is the writer of that article old enough to have been cognizant of the work professional IT people were doing at the time hell *I'm* not old enough, I just paid attention as an adult lmao

I was able to work a short term freelance gig for a couple local companies updating their software because I had learned COBOL the year before. Lots of people worked to make sure things went smoothly. They absolutely hated that a highschool kid had to do it for them 😂

Taylor Lorenz@taylorlorenz.bsky.social

The worst is when jealous male “media reporters” at mainstream outlets like CNN, Semafor, NPR etc take these made up narratives and publish them as articles as if it’s fact, then refuse to correct their stories even when provided with facts that completely debunk their claims!

Listened to that broadcast and got pretty miffed on y'alls behalf (young then). They downplayed the hard work & planning that went into making sure it wasn't a total catastrophe. Kinda reminds me of the "what do we need vax for, nobody gets polio any more" crowd. Not IT exactly, but I get why ur mad

The actual issue was very real and needed tons of work to fix. As with anything major, there was also tons of fear mongering and scams. People were slapping Y2K compliance stickers on things that never had a chance of breaking, selling BS insurance, etc…

She was making other claims that made no sense & proved she didn't even understand what the issues were. I sent her articles about what went on, factchecking the myths, & she said she didn't want to educate herself because was >20 years ago & they would've hidden any evidence showing

It was 18 months of serious preparation, and when the clock struck midnight on 1/1/2000 it wasn’t so much a sigh of relief as it was a victory celebration. Yes, it was 25 years ago, but a lot of us (that were sentient) are still here!

Am I missing something? The post points out that "years and billions of dollars were spent on painstaking preparation" and the linked story details many examples of all the work that was done to make it a mostly painless transition. It seems like a pretty decent framing?

One of NPR's dumber takes —been some doozies lately. I missed a couple of 'clocks' in my little fiefdom. Guess how I learned. And when you're running a college media platform linked to a university system it wasn't fun to find them after the fact either. A great success story of the tech world.

What’s the dumb take? That the y2k crisis was averted because of the incredibly hard work of thousands and also millions of dollars spent? Maybe go back and read the headline and if you’re feeling spicy the whole article too!

"In the end, the worst fears lay in anticipation. Besides a few minor setbacks like an internet slowdown and reports of malfunctioning clocks, the aggressive planning and recalibration paid off." Imagine talking about polio this way.

The article isn’t about how the effort was wasted, it’s literally about how it “paid off,” to quote directly from the article you didn’t bother to read.

I was responding to OP’s comment, saying that prevention is hard to see, due to its nature. People notice actions and consequences, not inaction or lack of consequences. e.g. insider trading = sell when you know a stock will tank. Not insider trading = hold when you know a stock will go up.

I was surprised by elevators needing reflashing or replacing control boards, apparently many of them used generic clock chips which by default ran a calendar. If your alarm clock crashes, you curse and turn it on and off again, if your lift controller crashes 20 stories up it's a different story,

Same. I didn't get to go to any New Year's parties that year. I was under orders to be at home, sober, by my phone, in case anything happens. So there my ass was, all alone, playing Railroad Tycoon, watching Dick Clark on TV, and waiting for a phone call that never came, because I did a good job.

I watched London's NYE fireworks that night from the roof of our office. We had a couple of minor problems that had somehow been missed (some buried Perl scripts that decided it was 1st January 19100 IIRC,) but on the whole a hell of a lot of preparation paid off.

4am rolled round and no phone calls, so I popped my first beer of the new millennium and tried to catch up with the rest of the party. Bonus was indeed awesome though - as was the overtime for the 9 months before

My company were based in airports none of my team wanted to cover the phone so I did it, I figured I could have a couple and be fine… Midnight rolled around and not a peep!

Y2K was a perfect example of a human-induced (potential) disaster, where even normally congenially people turned into hoarders and armed survivalists, as opposed to natural disasters, where everyone comes together. What's the difference?

If it’s any consolation, the actual radio segment was not as bad as this little teaser phrases it. V much discussing how it was a lot of grunt work to fix but the media was fixated on “end of world” narrative, because it’s much more thrilling than ppl sitting at desks working.

Heck, I’m not part of that career trajectory yet was one of those people who had the dubious privilege of making sure the law firm I worked for was Y2K ready. I joke that it’s because I was the only person in our office who understood that the floppy disk tray wasn’t a coffee cup holder.

Sadly it’s often the same with all things preventative: cyber security, supply chain security, CVEs, etc. How do you measure the investment when the nightmare scenario is avoided?

For real. In the mid/late 90s, companies came from out of the woodwork to contact folks I worked with (me a youngster at the time) who’d written code 20+ years prior. The industry was mobilized. The vaccine skeptic analogy is unfortunately apt.

Superman: * fills gap in train tracks with his body, train rides over without crashing into the canyon * People: See, nothing happened. Superman is lame! Yeah... welcome to IT

It's honestly a really poorly written headline. It should say "was averted" instead of "didn't live up to the hype." The latter implied that the gears were overblown and the prevention was unnecessary.

Are we just ignoring the fact that the article AND headline both acknowledge the money and work that went into averting the doomsday scenario? This is god tier levels of willful misinterpretation

A headline about how "it failed to live up to the hype" kind of more than offsets a buried lede about the time, effort, and expense involved. And that's with the 2038 problem bearing down on us...

Ok no you don’t get to use the term “burying the lede” when referring to text that is in the headline! That’s like someone who only read the first chapter of a book saying the author buried the lede by not saying how it ends in the first paragraph a la Romeo and Juliet XD

Yeah unfortunately there are two different but equally interesting narratives, one of the actual technical achievement that was avoiding the crisis, and the other, on how the media at the time caused a panic over “the end of the world” and trying to do both confused some readers

Agreed. I worked for an insurance company that spent a boat load of money on making sure everything would work on Y2K. I remember sitting in the office from 10 PM until 6 AM watching mainframe jobs complete. Nothing failed. I was sick as a dog and glad to go home after my shift to get sleep.

Same. Patching them all by hand with a floppy or CD. I missed one test system in a lab. An NT 4.0 server. On 1 January 2000 it just dropped off the network and was unreachable. Had to patched and rebooted. Can you imagine what would have happened without all the work done by IT folks in 1998-99?

I invented software that acted like malware that would search through the NT domain and install itself onto workstations and servers at a remote site audit the machine and then automatically deploy Y2K patches. We could then send a kill message so that my agent would remove itself later.

was just coming here to say we should just mandate constant supervision for people who haven't been on the internet since the 90s, between this and the person who claimed Google has never been good.

For real. For years leading up to that, I was getting regular head hunting calls to do y2k fixes. The industry effort to fix all that was huge. Next thing you know, they'll be talking about how the hole in the ozone layer was a nothingburger. (It wasn't).

I think 2038 is mostly handled, because everything is now behind interfaces that can be fixed with library patches. Still need to go through and make sure those updates are done, though, especially in critical embedded systems.

The big change is that so much is now on 64-bit hardware with time_t types to match. Moving to 64-bit kicks the can down the road a piece... to some point after the Sun has died.

Unfortunately not -- there is TONS of work to do for y2038 and it may be worse than Y2K. I worry that the limited impact during Y2K will result in some complacency. I've already started seeing y2038 problems in the field. The worst will be places where network protocols have Y2038 issues baked in.

Im assuming its built into a heap of hardware too / hopefully will all be replaced before that is an issue as well :/

I've got bad news, folks are already talking about the hole in the ozone layer that way and as proof that weather change isn't a thing (we are so screwed)

Right there with ya, man. We Y2K tested everything at our headquarters, then spend the better part of 2 months setting up a Y2K operations centre with the military, police, emergency services, and anyone else that needed to be there for the Y2K apocalypse .....and nothing happened.

And 20 years later, the controller for our pellet stove went into a boot loop on 1/1 2020, because the date rolled over to 1/1 1970. Nobody had updated the kernel in the linux it runs for all that time ..

I worked for an ISP that served all the universities and k-12 schools in our state. 60+ hours for over 8 months, mostly weekends and evenings to fix the 600 servers they identified as having issues. Many Solaris and IRIX servers that hadn't been touched that were mission critical.

On 12/31 we setup a war room to fix everything that got missed. A few modem banks went offline, our security system in the DC went offline, but that was about it, and we fixed those on the spot. Our NYE party was a cold sub and falling asleep at our desks.

Agree with you 💯. Worked first several years as a user liason to make sure we could still pay the bills and employees and keep the books when the year turned. A big team was dedicated to make this seamless transition.

If only the headline would have acknowledged the years and billions of dollars that were spent on painstaking preparations to ensure W2K didn’t live up to the hype. Oh wait… it did.

I spent months tracking down & fixing the infrastructure issues in a large UK council. We also set up paper based alternatives to everything so service would continue if we had missed anything. We did not. That work was mirrored across the world & Y2K was a huge success. Today? We would all burn.

The point was we didn't always know what was necessary, chasing vendors for certifications of network appliances, access control, security systems etc. and scheduling cutoff dates for certifications to ensure time for sourcing replacments and integrating them if necessary was a major PITA.

On a personal note I bought a new car from the proceeds of evening and weekend work I did for a Cobol software house I'd worked for in the early 80s, it's amazing how long mainframe and mini accounting systems hung around. it was drudgery but I got to catch up with peope I hadn't seen for ten years.

This is a really ignorant take. Didn’t live up to the hype? Like,‘it would’ve been more fun if everything failed? Any idea how much work by so many people went into making sure it didn’t “live up” to media’s hype?

I’d say they have a pretty good idea since the entire point of the article is pointing out how remediation efforts over the course of many years prevented the problem.

...ummmm... the description even reads, "...after years and billions of dollars were spent on painstaking preparation." Your painstaking preparation was acknowledged.

I was working in architecture at the time and the amount of angst over HVAC and elevator controllers was crazy. And 100% justified. Things would have just stopped working. The one thing I remember failing on Jan. 1, 2001 were elevators.

I dunno why I'm so kerfuffled at being included in this lol, but plenty of millennials are aware it wasn't a hoax. I was a little weirdo who was glued to the news even as a teen, but like... it was pretty well communicated at the time what the issue was, even at the lay level

Maybe an age difference? I was only 9 in 1999, and 9 year olds back then definitely didn’t have the tech savvy that 9 year olds have now. “Millennials” spans about 15 years so that would make sense. Probably also just varied from family to family as to understanding/threat level etc.

I would also add though there genuinely has been a massive movement to make Y2K a joke in the media and news. As they said before, disasters that don’t happen aren’t disasters. There is a *lot* of gaslighting involved. And this certainly isn’t the only thing to have that treatment in history.

If you're being serious, then the answer is yes, 100% real. Tons of effort was spent to patch or replace programs. COBOL programmers were called out of retirement to fix bank software. And in the end we got through with minimal disruption. People might've gotten more credit if more things broke?

No I’m 100% serious. I have no idea how to get that more across but it’s actually insane. My mom literally worked for tech companies in Silicon Valley my whole life and I was STILL convinced it was just a weird hoax that drove people insane for “no reason.” I’m not even sure she thought it was real

The fact that we were all convinced it wasn’t is wild. And I think you’re right. If bad things did happen it would’ve been, well, bad. I literally remember people stalking up their bunkers and everything. A version of Survivor bias, I guess.

What a weird world we live in! It almost feels like something out of a movie - except instead of the weary secret agent talking about all the plots they've foiled, and how the regular public will never know how close they came to disaster, it's the corporate IT veteran.

I worked at the Toronto Reference Library during the lead up to Y2K. We had an extensive retrospective collection of COBOL and other programming language texts that were in constant use, because all the banks in Canada are headquartered in Toronto, and there were jobs!

Problems were found in water treatment control systems. Easy to fix ,ladder logic is easy. The system ended up more resilient as quite a lot of date dependant stuff was moved out into the monitoring side.

What Y2K did do, however, for sysadmins like me, was it showed the value of automation, thorough documentation, and policy-based uniformity in desktop and server images. The free-for-all approach makes diagnostics too difficult at scale.

I think I personally upgraded core interface systems for some 50+ banks and I remember that there was one bank that was still running an older, non-compliant version of HPUX that never returned our calls.

My 2 patrners IT consulting and management company exploded because of Y2K. We had been growing steadily since 1992 but starting in 1998, growth was exponential. We were bought out by a large IT company in 2004 for a sum in the low 9 figures. I retired after. My share was in the middle 8 figures

I worked in an E.R. 1999-2000. They were still putting compliant stickers on medical machines on Dec. 28th because hospital administration waited so long to okay the start of the confirmation process for the building. We just hoped stuff would work after midnight.

It's the "IT Problem": - No problem: "Why do we need you?" - Everything's broken?: "What good are you?" I sometimes wish that just a few more high profile sites had failed in their Y2K prep if only so more people saw how close to the edge we came.

"Whatever happened to the hole in the ozone layer. Oh those scientists, always yelling about something" Yes my dude. Because we fucking fixed it. It took a shitload of work, but we fixed it. Grrrr.

a professional journalist actually wrote "Y2K didn't live up to the hype" and immediately after it wrote "after years and billions of dollars were spent on painstaking preparation" and didn't see what was happening there, jfc we are all doomed

The article is literally about how the preparation prevented the issue. What are you even talking about? The preparation paying off is the entire point.

That’s not what the article says at all. The article says the preparation “paid off” by averting the disaster. Maybe you should read it before commenting on it?

What's more impressive is you all had to work on old systems that used COBOL. And if there was any documentation, it was a printout with notes written on it because every bit was precious. It is scary how much we rely on things no one knows anymore.

I’m still traumatized by the the reams of COBOL code printout I had to review as an intern .. by the number of problems in the bank’s treasury system. I wanted to take all my money out of banks.