Daylight Savings +3
Ted writes that the new daylight savings schedule is like Y2K all over again. For me there are two reasons why he is wrong and one reason why he is right. But I agree that unlike Y2K this change probably causes more problems than it solves.
Two reasons this is not as bad: (1) I had to man a Y2K Command Post until midnight on New Years Eve. I still have the denim shirt with the Y2K C.P. logo to prove it. (2) With the help of a few elves, I helped craft a now famous poem, The Bad Y2K. It is famous because it is listed in Wikipedia on the Y2K article. I put it there. Gets about 1 hit per day with 5 pages per visit.
But in one very important way, Ted is right. It is Y2K all over again and even worse. Why? The two of us both had problems today. I had no problems on Y2K day. At work, I use a Mac and Windows XP. In Lotus Notes, all of my appointments showed 1 hour later for the next three weeks. On the Mac all of the appointments showed 1 hour early for the next three weeks. It hurts my head just trying to figure out why there is a difference of two hours here. But that isn't so hard to deal with. I just started off the day mentally subtracting an hour and only looked at my Dell. Except I showed up 1 hour early for my 3 o'clock meeting which showed as 4 and really turned out to be at 4. The host of the meeting laughed at me, which wouldn't be so bad, except this host happens to represent our whole division in the merger planning. "That Jeb... he can't tell time. We don't need anyone who can't tell time in the new organization."
For the real Y2K, there was no job threat. Just a really high quality denim shirt.
Note: Top ranking in Google:
At work they told us to write the time of the meeting in the meeting invitation to avoid confusion. It is a simple solution that would have worked great if anyone had actually done it.