Some Australian states have delayed their Daylight Savings time-switch by a week in order to accommodate the Commonwealth Games; however, this is causing chaos in corporate environments where the servers have no idea how to reconcile their time-zones and get everyone into the same meeting at the same time, correctly sort database entries by time, etc. It's only going to get worse next year, when some Canadian provinces change their Daylight Savings switch-dates to save electricity — time-zones are already ad-hoc, and nearly random (see the update to this post for more); once they start getting arbitrarily changed from year to year, it becomes practically impossible to keep track of them
The hitch is that the Microsoft Exchange server that we all use in Australia for my company is located in Kuala Lumpur, who I'm guessing didn't know about this deviation from standard DST. As a result, our Outlook calendars are showing that Adelaide are out of DST when they aren't.
The upshot of this is that some of the meetings in my calendar are actually an hour earlier than they appear to be. But only the ones that were booked by folks in Adelaide, and only for this week. As a result some people are putting the time of the meeting in the subject line (note the Tuesday 11am meeting below marked as "10am Perth time").
(Thanks, Stewart!)
