Most of the y2k problem was custom software, and really old embedded stuff. In my case, all our systems were fine at the OS, and I don’t remember any commercial software we had trouble with, but we had a lot of custom software it’s problems, as did our partners
Comment on CFCs
neidu2@feddit.nl 6 months agoI wasn’t working in the IT field back then, as I was only 16, but as I knew that it’d most likely be my field one day (yup, I was right), I followed this closely and applied patches accordingly.
Everything kept working fine except this one modem I had.
AA5B@lemmy.world 6 months ago
Dasnap@lemmy.world 6 months ago
And that modem was handling the nuke codes, right?
FunkFactory@lemmy.world 6 months ago
I kinda wish I knew what it was like working on Y2K stuff. It sounds like the most mundane bug to fix, but the problem is that it was everywhere. Which I imagine made it pretty expensive 👀
stringere@leminal.space 6 months ago
And computer networking, especially the ability to remote into a system and make changes or deliver updates en masse, was nowhere near as robust as it is today meaning a lot of those fixes were done manually.