| « The Hangar Management System | DOLLARS and SENSE » |
"Thank goodness this bicycle I'm borrowing still works after Y2K," Robin Sheat notes, "I can't even imagine the programmer-hours required to bring it up to spec."
Google's CSS How-To didn't inspire a whole lot of confidence in Stephen Schwarz.
"This error pops up every now and then," Jeff Pitcrew writes, "and this one in particular happened on May 1st. I do respect that they programmed their licensing to be flexible enough for two millennia in, presumably, either direction."
"Hmmmm," Jeremy Vanderburg pondered, "I've never heard of this sequel before... but who can keep up with such things these days."
Tyler Menezes notes, "apparently null wasn't the answer."
"I normally wouldn't send in all-too-common 500-Error," Brian Reiter wrote, "but this error from the website of Chicago Public Radio's This American Life is a head-scratcher on several levels."
|
The real expense with the bicycle was the testing. Since it doesn't have an onboard system clock to set forward, the team had to build a functional time machine and transport the bike (complete with brave rider) forward to the actual Y2K experience.
He didn't survive the trip back, to tell everyone that Y2K turned out to be a non event. But fortunately his test checklist -- nicely filled out -- was clipped to the bike making a second test unnecessary. Ahh the sacrifices... |
|
In 1999 I was working for a company that made thermal management products, in other words, heatsinks. Big finned blocks of aluminum. For each of the heatsink products they used GE made us fill out forms verifying that our big inert chunks of metal were ready for Y2K. They were very serious about it too, there were penalties for not filing the paperwork.
|
| « The Hangar Management System | DOLLARS and SENSE » |
