Do you have the time?

news : by Tommy — February 18th 2007, 12:58PM
newsI found this article over at PhysOrg.com talking about this year's change in Daylight Savings Time. Normally, DST occurs on the first weekend in April, but this year we'll begin on the 2nd weekend in March. We'll also end differently too. Rather than "fall back" on the last weekend in October, we'll end on the first Sunday in November.

Why are we changing? Well, it goes back to the Energy Policy Act of 2005 where we decided to conserve energy by time-shifting our days. Which isn't much different at all from the original reason we adopted DST in the first place. From what I remember from some long-past history lesson, we adopted DST to conserve energy sometime back around the Great Depression (although that link might not be proven, it's just what I remember). The whole notion of getting up earlier to get the day over with one hour earlier would have reduced energy consumption at night for all those who stayed up late. According to wikipedia, in 1976 the US Dept. of Transportation concluded that DST saves the US 1% of the national energy consumption. (It doesn't sound like much, but I'm sure it's a substantial dollar amount.) On the otherhand, I'm pretty sure we've become more of a 24/7 global society than we were back when we started DST, so it's quite possible that the savings aren't nearly as high. history>
The article highlights some issues with the time change. Remember this is a US policy change, not global, so when we "spring forward" there will only be a 4-hour difference between GMT and EST instead of the 5-hour difference normally. Confusing enough? Think about any consumer devices that aren't linked to the national clock or some time setting service. It could be trouble for some people.

The article is likening it to another Y2K, and I agree. It'll be hyped by the media one day, but will fizzle out in reality.

Comments

Paul A. Feb 19, 2007 08:15
This new time shift wreaks havoc with Microsoft Windows and Outlook. There is a patch out that is supposed to fix the DST issue. However, even after applying this patch, it still messes up your appointments. Someone I knew ended up with an appointment in the year 2085 after applying the patch.

More info here
Tommy G. Feb 21, 2007 01:22


anonymous Feb 24, 2007 11:17
Yeah this issue is being treated with all the respect that Y2K did at AMD. We have full-fledged action plans, area owners, and the goal is to unequivocally verify that all software that we use in our environment will make the time change automatically and correctly to avoid any operational issues. Software like SAP is the most critical, and because it runs on Windows, who knows what will end up happening. I'm just glad that I'm only dealing with Linux boxes, which for the most part use Epoch time to calculate stuff, which makes the transition a lot easier (new /etc/localtime, reboot, voila! then anything using glibc gets correct date info).
anonymous Mar 21, 2007 11:17
Anyone die? Any companies explode?

Didn't think so, Y2K - pfft.

Sign in or create an account to leave a comment.