[DRB]

http://www.msnbc.msn.com/id/16912614/

It seemed so simple and familiar: Spring forward, fall back. For 20 years, that's what Americans -- and their technology -- have done with their clocks on the first Sunday in April and the last Sunday in October.

No longer. When few people were paying attention in August 2005, Congress lengthened daylight saving time by four weeks in the name of energy efficiency.

The change takes effect this year -- on March 11 -- and it has angered airlines, delighted candy makers and sent thousands of technicians scrambling to make sure countless automated systems switch their clocks at the right moment. Unless changed by one method or another, many systems will remain programmed to read the calendar and start daylight saving time on its old date in April, not its new one in March.

Its actually a big deal for a number of my clients and they are borderline paniced. Lots of systems are very much time specific and a change like that could cause some issues.

 

[SkaredShtles]

We are currently getting our a$$es handed to us at work because of this issue.

 

[Westy]

We keep getting questioned about this on our industrial controls. Our answer is 'we never had daylight savings programmed into the clock anyway, you are no more ****ed than you have been in years past'.

 

[SkaredShtles]

Another great argument for using UTC and nothing else.

 

[valve bouncer]

They suddenly bought daylight saving in in Western Australia in December. Didn't hear of any problems.
WA didn't have daylight saving previously and it wasn't on the agenda even until October so the change was sudden.

 

[binary visions]

They suddenly bought daylight saving in in Western Australia in December. Didn't hear of any problems.

That's because the problem only affects computers, not beer, sheep or barbeques.

 

[SkaredShtles]

That's because the problem only affects computers, not beer, sheep or barbeques.

Post of the Day!