Speaking as someone from the tech sector DST is a pain in the butt. So imagine trying to compute, for example, timecards. You clocked in at 12:00am and clocked out at 6:00am. Looks like 6 hrs on shift. Not so on March 11, 2007 2:00am-2:59am never happened! We went straight to 3:00am from 1:59am.
So all these technical systems have special logic that say timespan = end - start UNLESS it's the 1st Sunday in April. But wait, Congress steps in and changes all of that. So we all patch our systems, try and figure out how to fix this mess. And for what?
As far as the purpose[—energy conservation—]of the move is concerned, that appears to be a total flopNothing.
And it seems as if some of us techies screwed up.
if you're wondering why some of your colleagues showed up late for work yesterday, it's because many devices-even patched devices-shifted an hour ahead Sunday, when the change would have normally taken place.This is not surprising since there are hundreds, thousands, no, millions of places we do this kind of calculation