Picture this: it’s January 19th, 2038, at exactly 03:14:07 UTC. Somewhere in a data center, a Unix system quietly ticks over its internal clock counter one more time. But instead of moving fo…
Y2K wasn’t overhyped. It was just successfully planned for. This reeks of the paradox of IT. “Everything is broken, what do you even do” vs “nothing is broken, what do you even do?”
Yeah it only felt like it wasn’t a big deal because it became a big deal early enough for there to be plans made. And because good people doing hard work to prevent a problem wasn’t newsworthy after the fact.
I was at Pepsi for Y2K. In 98, we started with MSMail, W95, and Netware2. We had to also replace all 40k desktops. We worked like dogs for those 2 years and only barely had everything ready in time. Without that work, we would not have been able to continue any business operations. Nothing about it was overhyped.
deleted by creator
Y2K wasn’t overhyped. It was just successfully planned for. This reeks of the paradox of IT. “Everything is broken, what do you even do” vs “nothing is broken, what do you even do?”
Yeah it only felt like it wasn’t a big deal because it became a big deal early enough for there to be plans made. And because good people doing hard work to prevent a problem wasn’t newsworthy after the fact.
That’s the thing though: It was well-prepared and due to that there was no big issue.
2038 is the same: very well prepared and thus it will not be a big issue.
Of course, if ignored, both would be very problematic, but that’s not the point.
I was at Pepsi for Y2K. In 98, we started with MSMail, W95, and Netware2. We had to also replace all 40k desktops. We worked like dogs for those 2 years and only barely had everything ready in time. Without that work, we would not have been able to continue any business operations. Nothing about it was overhyped.