|
|
|
| Non-WTF Job: 4 Senior C# Developers Needed Now! (Cincinnati, OH) |
| « Source Control Mastery | Hypothetical Question & Tales From The Dump » |
"After close consideration," writes Nick, "I've decided that my mayo really expired on Feb 19, 2008, not 1908. Apparently, Y2K bugs never seem to expire...
"Ummmm....," an anonymous reader pondered, "yes?"
Remember a few months back when the internet went down? Some say it had something to do with undersea cables... but Ferdy is pretty sure he just clicked "Yes".
Anthony Chambers said, "thank goodness there was no error displaying this error!"
This popped up for Sebastiaan when he tried to uninstall some obscure application...
The irony here is that Rick did this search from within a Radio Shack store...
"50% off!?," Dan noted, "with those kind of savings, I could start two wars in Iraq!"
"While doing the business taxes for my company," noted Ennis Ray Lynch, Jr., "I was a little surprised at my potential expiration dates. I guess sometimes December comes before May.
Local time. The mayo jar has an atomic clock and GPS built into it. |
|
Nick, it doesn't matter if that Mayo expired Feb 1908 or Feb 19, 2008 because it expired a while ago. That is unless FEB1908C is month followed by year in hex... then it would be good for another 100532 years. Then again, the whole date could be in hex.
|
Re: A Y2K Holdover
2008-07-02 09:55
•
by
vambala
(unregistered)
|
Exactly. So if you realize that your mayo just expired a few minutes ago you should very quickly send it to someone who lives in a different time zone. (in western direction). Then it will be usable again for a short time... |
| « Source Control Mastery | Hypothetical Question & Tales From The Dump » |