I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
-
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
@johnzajac prevention paradox strikes again! (I'm working in public health and the whole of it is basically prevention)
-
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
. We worked like animals to fix the code. -
@johnzajac worthwhile pointing out that many websites displayed an impossible time due to a Y2K issue in Perl. The world did not stop.
Also, the consulting companies made out like bandits. They used the concept of Y2K compliance to drive business.
Because of that I am always cautious about Y2K as an analogy.
@glent @johnzajac the current Perl error comment is a classic example of survivorship bias - https://en.wikipedia.org/wiki/Survivorship_bias
That’s the bullethole that did not disable the plane(or world wide computer network)Y2K impact would have been the equivalent of every Amazon, Microsoft, Apple and Oracle datacenter shutting off at the same instant in time and going offline.
ATMs, Supermarket Point of sales, planes, power stations, etc. all going offline too. -
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
@johnzajac the most recent Y2K failure i saw was only a few years ago, when a liquor store sign told me i couldn't buy alcohol unless i was born after this day in 1900.
i've been telling non-tech people about fixing a lot of Y2K38 stuff lately, including the "this is why Y2K wasn't a problem - we fixed it" part. there were so many basic issues including "system won't boot" that would have awful to deal with. also, IMO, Y2K38 is a harder problem... i plan to skip Y2106 issues.
-
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
@johnzajac vaccines
-
Why should my taxes pay for a "fire department"? My house isn't on fire!
[since I can't quote-boost it]
"Why should my taxes pay for a "fire department"? My house isn't on fire!"The real problem is that they then demand that the fire get put out at cost without understanding that the cost is cheaper when you do prevention.
This is one of the reasons that US health care is so expensive. People use emergency rooms for basic health care, which they only go to when things get so bad they have to. Because health care premiums and copays and deductables are so high.
-
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
@johnzajac there's a handful of these kinds of things, getting the ozone layer to recover was another one. Underappreciated efforts spread out globally and backed by massive amounts of paperwork that actually did a thing.
-
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
@johnzajac As always: There is no glory in prevention.
-
@johnzajac the most recent Y2K failure i saw was only a few years ago, when a liquor store sign told me i couldn't buy alcohol unless i was born after this day in 1900.
i've been telling non-tech people about fixing a lot of Y2K38 stuff lately, including the "this is why Y2K wasn't a problem - we fixed it" part. there were so many basic issues including "system won't boot" that would have awful to deal with. also, IMO, Y2K38 is a harder problem... i plan to skip Y2106 issues.
Well, the liquor store sign is not *wrong*. No one born in 1900, or before can buy alcohol today. It's a moot point, as they're all dead.
(And I'm assuming that the sign actually said "on or before," not "after.")
-
@johnzajac the most recent Y2K failure i saw was only a few years ago, when a liquor store sign told me i couldn't buy alcohol unless i was born after this day in 1900.
i've been telling non-tech people about fixing a lot of Y2K38 stuff lately, including the "this is why Y2K wasn't a problem - we fixed it" part. there were so many basic issues including "system won't boot" that would have awful to deal with. also, IMO, Y2K38 is a harder problem... i plan to skip Y2106 issues.
I'm working on the Y10K problem. I'm a real forward-thinker.
And, actually, in reality, I'm having a remarkably hard time convincing my superiors that there are really problems with a bunch of files we have, ... in spite of the fact that one of them even has a five digit year in it. Parsing error and the file can't be used, of course. So it *is* a real-world example of the Y10K bug. (And a typo, as that field can only have past dates, and 22025 is in the future)
-
I wish we had spent the last 26 years teaching people that the reason the 2000 bug didn't destroy a significant amount of our infrastructure is because *we caught it* and *spent thousands of hours fixing it* BEFORE the year 2000
Because within that little perplexion - people thinking the problem was a hoax because it was fixed before it destroyed shit - is an encapsulation of the current era of Western politics, including COVID mitigation, lesser evil politics, fascism, and crime rate hyperbole
It's very hard to get people to care about infrastructure, because it's boring.
Future problems are even more boring.
I do find the concept of "technical debt" (as flawed as it is) is useful to get people thinking about infrastructure.
-
J jwcph@helvede.net shared this topic
