Dear Drafters of the Energy Policy Act of 2005,
By moving the start of Daylight Saving Time back three weeks, and the end of DST forward one week, you’ve created four weeks of annual electronic chaos. I was busy enough last year updating time zone files and implementing network time servers. I thought such an opportunity would never roll around again, but I was wrong. It seems that when people set up computers, they’ll install security packs and updated drivers, but they won’t ever remember to update time zone files.
And let’s not even talk about legacy systems. The time clock from 1996, the PBX from 1987, the rickety Exchange server in the closet, the mission-critical Java apps, and the routing daemon written in positively barbaric Perl? No patches exist for any of those. Don’t think I didn’t look. Companies go out of business, cease supporting old products, lose their original source code, and make extremely bad decisions all the time. So unless anybody stuck with any of the above forks out a buttload of cash (or, more realistically, convinces their superiors to do the forking) there will be three annual weeks of chaos in the spring, and one in the fall.
The fact that these periods of chaos abruptly cease means that once the superiors’ calendars spontaneously snap back to normal, the problem will be forgotten, and the hoped-for buttloads of cash will instead be forked into new bad decisions.
In my humble opinion, the result of this Act has been an overall waste of energy— particularly by myself— which will continue into the foreseeable future. Well done, Drafters of the Energy Policy Act of 2005. But least there are now 28 more hours annually of afternoon sunlight, all the better for the Sporting Goods Manufacturers Association and the National Association of Convenience Stores to, er, stimulate the economy.
The Electronic Replicant