Rob Napier @cocoaphony@mastodon.social
Quiet public

RE: dice.camp/@johnzajac/115845954

I spent a lot of time in the 90s working on Y2K. It wasn't a huge panic. It was just a slice out of everything else we spent auditing code. It wasn't "spend 80 hours a week fixing this." It was just boring. Incredibly boring. And we made it be ok by being bored and fixing stuff.

And the one thing I never thought would happen was that people would say it was never a problem. Oh good grief, it was a problem. All over. We just fixed it. Like we thought grownups should do when there's a problem.

0
0
1

If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/cocoaphony/statuses/115913806013557052 on your instance and quote it. (Note that quoting is not supported in Mastodon.)

Bodil @bodil@treehouse.systems
Quiet public

I was doing web dev and running Linux servers for a living in the late 90s. I can assure you the Y2K bug was not something I even worried about in that line of work, because we were working on systems not written in COBOL by idiots to run on mainframes from the 60s. You see, only an idiot would think it could be a good idea to encode a date with a fixed two character year. We were smart, forward thinking people who encoded our dates in intelligently future proof formats which won't fail until 2038, a date so far into the future as to be purely theoretical.

https://mastodon.social/users/cocoaphony/statuses/115913806013557052
0
0
0