New Year’s Eve: Musings on Y2K
At 3pm PST on 31 December, 1999, I sat down at the computer in my home office in Yakima, Washington. I logged remotely into the network at HQ and started monitoring our systems. The most critical moment would come at 4pm local time. We were in Pacific Standard Time (PST), -0800 UTC. In other words, at 4pm in Yakima, it would be midnight in Greenwich, England, where the time zone aligns with Coordinated Universal Time. (Coordinated Universal Time is abbreviated as UTC, not CUT, because there are actually other languages in the world besides English, and… never mind. Look it up if that story interests you).
Anyway.
The GPS satellites run on UTC, and our entire multi-state operation depended on GPS timing. My first hint of system failure because of a Y2K bug would occur at midnight, UTC.
Beginning at 3:55pm I began testing the major system once a minute. At 4:05pm I sent out the notice to corporate management that all was well.
I tested hourly, then, but the next critical moment wasn’t until 9pm PST, which was when midnight occurred on the US East Coast. Our equipment was all in MST and PST, but some of our many telecom providers might have systems with local time coordination in some other US time zone. (They’d all be using GPS now, but – this was 1999, and US telecommunications had plenty of legacy systems with other clocking methods).
In the end, nothing failed. Our entire system worked.
This wasn’t because Y2K was overblown.
It was because we replaced our billing system, which wasn’t able to generate an invoice after the date flip.
It was because we did software updates on several proprietary systems that would have failed.
It was because we did firmware updates, too.
Equipment inventories.
Application inventories.
Operating system inventories.
Software version inventories.
Firmware version inventories.
The reason January 1, 2000 seemed like such an ordinary day is because of the MASSIVE amount of work and money spent to make it ordinary. There are unsung heroes around the world who put in the work to update or replace systems that would’ve failed otherwise.
If you’re one of those people, I would love to hear your story.
@robertatcara As someone who personally discovered and fixed Y2K bugs that would have had significant real world impact, it is disturbing to hear someone propagate this myth [that it was a "big fuss about nothing"]. And it is a myth.
The testing methodology insured that these impacts were not hypothetical. At my company, the testing was performed by actually rolling the clock forward to test systems to see what would happen. For example, I discovered that every ATM in the state of Alaska operated by my company would have locked up until a PROM chip was swapped. Someone had to fly all over the state to proactively swap the chip beforehand, to avoid significant customer impact.
And that was just one story. I personally oversaw investigation and fixes for other hardware and software at that company that would have failed.
And that was just my company. I spoke with others in IT at that time with similar stories. And that was just the people I knew.
So no, it wasn't "a big fuss about nothing" - and saying so is both dangerously revisionist, and disrespectful of the work it took to prevent real impacts.
rn I'm doing a lot of research on early internet fandom for my bachelor thesis and since I was born after the turn of the millennium it's making me wonder how it must have been to be a fan on the internet when Usenet and ICQ/IRC/AIM and GeoCities were still a thing. It really feels like having some kind of lost nostalgia, I've only lived to see early facebook, msn and flipnote as my early internet interactions.
If you were a fan on the internet in the late 90's / early 00's, or know someone that was, please hit me up!! I'd love to have a chat about it!!
(please boost for coverage)
Just learned about #DecRecs! To make up for yesterday, Day 1 of Dec Recs I'll recommend this Chinese short animated series "All Saints Street" with four seasons. An angel, vampire, mummy, zombie, and werewolf live together. What could go wrong? Really enjoy it for the combination of great art, slice of life, and the supernatural. There's also a comic. It's produced similar to "Hey your cat ears are showing" but more memes and skulls than wholesome uwu. https://anilist.co/anime/114555#anime
For Day 4 of #DecRecs I'm going to cheat a little by recommending 3 short audio docs (podcast format) folx interested in learning more about an underrated topic.
🔥"Chester is Rising" (5 eps): the 30+ year grassroots Environmental Justice movement in the city home to the USA's largest incinerator among other major polluters. https://rss.com/podcasts/chesterisrising/
✊"March On: The Fight for Pride" (5 eps): the complicated history behind Philadelphia's pride march, including internalized racism and transphobia, and the work to heal and create something new https://whyy.org/programs/march-on/
🪲"Headlong: Surviving Y2K" (6 eps): despite the 2000's millennium bug being an afterthought for many, we explore the stories of those who were impacted by it personally, even years later https://topicstudios.com/podcasts/headlong-surviving-y2k/ #podcasts#nonfiction#storytelling#environmentalJustice#lgbt#philadelphia#philly#y2k