Y2K and 2038 xkcd.com/2697/ m.xkcd.com/2697/
@xkcdComic This is a notice for those who are presumptive and imprecise in their data generation.
@xkcdComic Fun fact - as a work around, some code was modified to _assume_ if YY > 25 (or 20, or 30 in some cases) the YYYY must be 19yy. No one would still be running the same software 20 years later right? Right?!? *cough*mainframe*cough*
@xkcdComic Still hoping to retire a year or two early and letting someone else deal with 2038.
@xkcdComic Alt text @ explainxkcd.com/wiki/index.php… Title text: "It's taken me 20 years, but I've finally finished rebuilding all my software to use 33-bit signed ints."
@xkcdComic Why is 2038 bad? (I don't know anything about computing)
@xkcdComic We actually ran into an issue the other day where a date was being displayed with 2-digit year and then that got copied and pasted into a new entry, so an expiration of 9999 became 1999. So Y2K may not be completely behind us...