Saturday, March 01, 2008

Google Calendar and Daylight Saving Time

This is blowing my mind, right now. It's making me twitch, because I cannot possibly fathom how some (normally smart) developer could have possibly thought this was a good idea. Here's the real WTF:

I put in a haircut appointment for myself, to occur on March 29, at 10:30 AM. Because, that's when it is--10:30 AM. Of course, we transition to Daylight Saving Time between now and then. I know this, but ... and here is the kicker ... Google Calendar thinks my appointment should be entered at 11:30 AM, because, well ... you know, because there's a time change.

Uh, huh. I'm stupid, and I don't know that 10:30 in four weeks is really 11:30 now. But of course, I'm not really confused because I know my hairdresser expects me to come in at 10:30 on that date. I have a little card that says so. It doesn't matter if it will be 10:30 AM EST or DST, it's still just 10:30 to us.

But Google, being much smarter than I am, really wants me to know that it's going to be 11:30 AM. I suppose that would work if I don't change my clocks, but we all know I will be changing my clocks, don't we?

This deserves to be posted on The Daily WTF, but I think I'll just keep this joke to myself. I posted a note to the "Users Troubleshooting" forum at Google, and we'll see what kind of reply I get. I can't wait for someone to tell me I did it wrong, because, like, you know, it's got to be all my fault.

3 Comments:

At 6/12/2008 5:47 PM, Blogger AdLentis said...

Well, I agree with you. I encountered the problem when syncing... my repeated appointment duplicates because of the bug, since after the DST change, it moved from 20:00 to 21:00 in Google Calendar, but it remained at 20:00 on my phone. Ugh. Ugly.

 
At 10/26/2009 5:09 AM, Blogger OndÅ™ej said...

Hi. It's now year and half since then and the WTF google has done it to my repeated entries once more! I can't even be sure if it is exactly the repeated entries that have shifted, or some others as well!

 
At 10/26/2009 3:31 PM, Blogger Corrine said...

I just encountered this problem too. :-(

 

Post a Comment

<< Home