NTP epoch in 2036 is going to be better since it isn't getting any attention and there's going to be no shortage of broken IoT devices that fail.

For the curious: https://doc.ntp.org/reflib/y2k/. 2^32 seconds since 1900-01-01 00:00 ends on 7 Feb 2036. The 2038 problem is 2^31 seconds since 1970-01-01 00:00, the Unix epoch.

Y2038 programming is my retirement plan. I’ll be around 60 and probably kicked out of Silicon Valley employability due to ageism. Like the cobol programmers in the 90s, in 2038 they will be scrambling to find old farts who still know C and UNIX.

C++ and Java are gonna be the obscure legacy languages. Plain bare-metal C is still a valid option for "baby's first programming language" today due to the popularity of Arduino.

Sounds like I should get back into Unix dev around 2034 maybe.

We're gonna party like it's 1999!

Actually, we'll probably be partying like it's Fri Dec 13 1901 20:45:52 GMT.

Ooh, Friday the 13th too, ominous.

Oh jeez, it's going to be so much worse than y2k.

At least we won't have to suffer though the 2106 problem.