Having watched another video saying Y2K wasn’t real - my standard clarification

[drwho@masto.hackers.town]

@jonn_blanchard <weeps in frustration...>

[decadecity@hachyderm.io]

@jonn_blanchard As a rookie field engineer going around patching stuff I wasn't working on anything as big as banks, hospitals or mass transport but I did see a lot of small businesses that would have been crippled by the loss of their IT capabilities.

[bencotterill@mastodon.social]

@jonn_blanchard @Binder My dad spent that night looking at screens. One thing that went wrong was the urinalysis checker in a toilet at a nuclear power station.

[cynblogger@sfba.social]

@jonn_blanchard
I had the world’s best programmer who started planning 24 years ahead. ️

[resuna@ohai.social]

@peteri @jonn_blanchard

And that doesn't address the y2k failures that happened basically every 5 years after 2000 as software where the problem was "solved" by redefining the rollover date using a window rolled over.

[cj@dragonscave.space]

@jonn_blanchard @Fragglemuppet If you put the work in up front then it always looks too easy. We just rolled out a huge project across multiple states with no issues at all. I don't think people realize how amazing this was because we just made it look too easy. It was three years of hard work with a one year sprint at the end.

[alsvha@sunny.garden]

@jonn_blanchard I actually think if the media hadn't blown the situation up as they did, I'm not sure so many would have actually cared about fixing it either.

It definitely was real, but conspiracy theories exists in all walks of life, so I guess it's just par for the course that (some) people doubt Y2K.

[svelmoe@hachyderm.io]

@jonn_blanchard I work on a live project which still contain handling of 2 digit year.

Stuff would have blown up if not done correctly.

[dacig@mastodon.social]

@jonn_blanchard Sorry to be a little sceptical (and not wanting to demean anybody's job) but...I don't remember any major disruption.
How to reconcile that with thousands (millions) of systems that were under peril to fail, and yet not one big enough to notice.
I mean, how come no major issue fell through the cracks? Were engineers 100% succesfull?

[jonn_blanchard@retrochat.online]

@dacig they did, there are accounts of things that failed. And not every system was affected, more “modern” systems that weren’t designed in an age where every byte was important didn’t have the same issues

[markhburton@mstdn.social]

@jonn_blanchard
Y2K was indeed real.

As an aside, the best, tongue in cheek, marketing ploy of those days was the Y2K compliant vegetable brush.

[jonn_blanchard@retrochat.online]

@markhburton so many companies had weird products to take advantage of the worry

[deborahh@cosocial.ca]

@jonn_blanchard @ShaulaEvans same

[jfrench@cupoftea.social]

@jonn_blanchard being on call on Jan 1 2000 was the most lucrative hangover I ever had

[mansr@society.oftrolls.com]

@sverx @jonn_blanchard I'd like to know what kind of reasoning led someone to implement the 100 year exception for leap years while deeming the 400 year one too much effort when they could have got away (until 2100) with doing neither.

[sverx@mastodon.gamedev.place]

@mansr @jonn_blanchard I remember discussing with colleagues back then and only *some* of them knew the rule about the 100 years exception, but *none* of them knew about the rule of the 400 years exception to the exception.

I bet also some of the people fixing the programs for Y2K were unaware of some of those rules...