5 ms·
A friend of mine was telling me how he spun up a consultancy and made enough to retire off the back of Y2K. Must be time to spin up one for Y2K38 and make bank
by cube00 5y ago
A friend of mine was telling me how he spun up a consultancy and made enough to retire off the back of Y2K. Must be time to spin up one for Y2K38 and make bank again.
- 14 5y agoDo you remember the mass hysteria and people running out and buying generators and flashlights and survival supplies? My aunt thought it would be the end of the world and bought a bunch of supplies in case everything stopped working.
- ianlevesque 5y agoBetter to be prepared and not need it than…well, you saw the last two years.
- spullara 5y agoIf the worked hadn't been done, that is probably what would have happened.
- doublepg23 5y agoFor sure. It's pretty easy to verify what would happen w.r.t. Y2K - you just change the clock...and things broke. LGR did an excellent video [1] on the subject. [1] https://youtu.be/Xm5OiB3CPxg https://youtu.be/Xm5OiB3CPxg
- eru 5y agoWhat makes you think so? My guess is that there would have been some minor disturbances; bureaucratic snafus about life insurance and so on. But unlikely to be a collapse of society.
- d0gsg0w00f 5y agoMy cheapo generator from Home Depot has Bluetooth so it probably won't work on 2039 /s I think it's so you can monitor the fuel level from inside your RV or something.
- dumbfoundded 5y agoYou should just make the right npm package. You could call it: "probably_correct_time" and it'd just add 137 to the year if it was less than 1937 or so. Then raise some money to fund AI research to decipher if it's about the great depression or something to guess the right year. I joke but honestly someone is going to build this and then get acquired by Grammarly.
- partomniscient 5y agoSome companies used this approach for Y2K, deciding to use a pivot similar to the above to decide whether to prefix 19 or 20 (or 21 or 22). It made the fix easy, but they didn't expand the field size from YY to CCYY, so all kinds of stupid errors await us in the future. I was young at the time, and I did what management told me to do but felt icky about it because I knew it was hugely inferior and they didn't know what they were doing, and I was just a tiny cog in the team doing all the changes, most of which thought it was fine... Left that place long ago. What you recommend is an easy fix, and might work most of the time, but its wrong and will cause infuriating problems, probably making others suffer your past deeds. Just do it properly once, first time.
- dumbfoundded 5y agoI completely agree and it's why I wrote it as a joke. Companies/Tools/Projects that plan to exist beyond 2038 should just migrate their code.