A lot longer than that...Y2K was the result of corpos prioritizing doing things as cheaply as possible and kicking the can down the road for 4 plus decades at that point, and when they finally decided to fix it before it blew up in their faces, it was almost too late and the software engineers were forced to hack a solution to buy another decade, then promptly got canned when "nothing happened" (leading to Y2K10 actually causing some problems when it rolled around)

We'll have another reckoning with this same class of error in January 2038 when the 32-bit UNIX epoch ends, and I have no doubt it'll be a shit show with a lot of pushback against anyone trying to fix it because we "whined" so much with Y2K...

Sorry... Don't drink and rant...