Thanks to George W Bush, Daylight Saving Time came early.  God knows how much brain and blood cells I lost over this.  I thought that we got all our servers and computers and whatnots covered with the new DST times, but turns out that some dude named Olson decided in late 2005 that the strict definition of EST (Eastern Standard Time) and MST (Mountain Standard Time) time zones do not suffer the indignity of daylight saving. 

Of course, I just found this out today, 3 days after the fact.  Apparently it's our fault because we should have converted customers in EST and MST to America/New_York and America/Denver time zones, respectively, which do change with DST.  Right.  Who in their right mind would change the definition of EST and MST but not CST and PST and then tell nobody about it.  Blah.  UNLESS YOU'RE STEPHEN HAWKING, DON'T FRIGGING PLAY WITH TIME!

So all my Eastern seaboard customers have their data lagging by one hour (who gives a hoot about Mountain people anyway?).  Now that my customer service folks are deaf from all the phone calls, it's my turn to suffer the consequences.

What am I going to do?  I am writing code on the fly to fix the live production database.  What does that mean in laymen terms?  Well, I am going to directly perform surgery on our customer's data, but because there is so much data, even my inner Cylon can't possibly do them fast them by hand, so I'm writing software to do it.  Software that normally usually takes a couple of days to do and then a couple of weeks to test, except that I wrote it up in an hour and the testing is unleashing on an unsuspecting victimcustomer.  Hey, if Microsoft can do it, so can I!

No safety, no backups, no problem, dude!  You think I'm nervous?

Let's hope I can make it to Pi day celebrations tonight.