March 11 daylight savings time is in effect, ahead 3 weeks this year. I think that this is going to be a huge problem for system admins. Every Windows machine has to be patched so that the clock will change at the correct time. If you aren’t patched you will be an hour behind. Computer A (patched) thinks its 10am, Computer B (not patched) thinks its 9am. For any type of application that uses a clock for a sync or timestamp, I have to think this is a problem, especially if they travel across different servers. Its Y2k all over again. Here’s an example of a problem with Google calenders.
Earlier today I descided I had an important meeting I should schedule March 26th. So I schedule the meeting for 10am, and I want to add a reminder to my Google calender. So I use the gadget on my personal homepage to add the appointment. Click on the date, write in the description, Google is cool to take the 10am in the beginning and schedule it as a timed appointment. But then look what happens!!
I said 10am! not 11am! O boy. Now we can get all scientific or whatever and say that 10am today will be 11am on March 26th, but the fact is I wanted the appointment at 10am, and on the 26th the meeting will be at 10. If we have this sort of issue on a simple Google calender, imagine what other things could go wrong! Nobody is freaking out about this like Y2k, and I think its going to be a real problem. Buy all the bottled water you can!!