> We considered a number of options, but decided that the fix was not making it about dates at all but rather offsets (e.g. "t+1 year", "t+2 years", etc.), which bypassed the Y2038 issue.
> We then immediately called something else to do the final translation into dates for the CSV.
"Postscript: there's lots more that I think would be interesting to say on this matter that won't fit in a tweet."
So... you send out another 20 tweets just like you did to make this story complete to get to the Postscript. Not sure why this story was okay to share in multiple tweets but his postscript wouldn't work in the same manner
This is great news! I spent most of my career writing in C and C++. I've been waiting for the 2038 bug to become a 'thing' so that I can emerge from retirement and charge people $700 an hour to fix their broken systems, just like Fortran programmers came out of retirement to fix the Y2K bug.
4 comments
[ 4.7 ms ] story [ 23.5 ms ] thread> We considered a number of options, but decided that the fix was not making it about dates at all but rather offsets (e.g. "t+1 year", "t+2 years", etc.), which bypassed the Y2038 issue.
> We then immediately called something else to do the final translation into dates for the CSV.
So... you send out another 20 tweets just like you did to make this story complete to get to the Postscript. Not sure why this story was okay to share in multiple tweets but his postscript wouldn't work in the same manner