Wait, what? What's the context for this call? Weirdly, I know COBOL. Eons ago, I learned it for a job that was fairly lucrative, well, for my very broke self. This call is right next to my dream of volunteering to do an emergency lit review when they call for a doctor on board.
The governor of New Jersey just put out the call on live TV that he is desperate for Cobol programmers right now.
18
23
4
303
I did get a shot at my other "dream" question and asked a surgeon if I would be able to play the piano after my hand surgery. (In case not obvious: I never did learn play the piano beyond a very rudimentary level so always wanted to ask! I was reassured, yes!)
1
2
54
By the way, just like SARS, Y2K was a near-miss. We should learn from near-misses. Many programmers worked very hard to avoid a catastrophe and fixed legacy code. I saw two-digit year variables in the nineties! There was a lot to clean up, and people did. Hence no big crisis.
14
50
9
220
Replying to @zeynep
Y2K is now farther in the past than January 2038 is in the future. In January 2038, the common signed 32-bit time representation (seconds since January 1, 1970, 00:00 UTC) overflows & resets back to December 1901. People ought to start being worried about what will break then.

Apr 5, 2020 · 4:20 AM UTC

3
6
14
Replying to @davidbaron @zeynep
Stuff has already broken. E.g., expiration dates of 30-year mortgages have been out past Y2K38 since '08. A lot of systems switched over to 64-bit time_t's years ago, which don't have that problem. But I'm sure there will still be lots of legacy hardware and file formats then.
Replying to @davidbaron @zeynep
Yes, OpenBSD already patched and mitigated all instances of 32bit Unix epoch time by release 5.5. So if you mean, people out to start being worried about it, others already fixed such problems. Keep up, you're way behind. ;-/
2