It is that time again. Daylight Savings Time is upon us once again as now we have to fall back. But is our technology falling behind? In a recent article in Howstuffworks.com, the topic of why would daylight-saving time mess up my computer is explored. In 2005, the U.S. Congress mandated a change in the daylight-saving time schedule that took effect earlier this year. On March 11, we turned our clocks forward three weeks earlier than usual; on November 4, we'll turn them back one week later, the idea being we'll get some energy savings out of the longer period of evening sunlight. While this seems like a smart idea, this mandate soon became a nightmare for IT professionals. You might be thinking that since the device updates itself by synching with some omniscient world clock, it'll still get the correct time, adjusted for the correct daylight-saving date. Because, you know, it's omniscient. In reality, that world clock is a whole bunch of "time servers" maintained by various agencies, and they all serve up a single time: Greenwich Mean Time, or "universal time." Once your device gets the Greenwich Mean Time, it calculates the correct time for your location by adding or subtracting hours based on your time zone and any daylight-saving adjustments for which it's been programmed. Any computer that was programmed before 2005 thinks daylight-saving started the first Sunday in April, not on March 11, and ended in October, not November. The real problem with the change in time is with businesses. Many activities such as time-sensitive payments and applications like scheduled meetings, scheduled stock trades, scheduled bank deposits, time clocks, and large networks -- especially international ones -- that rely on a variety of synched devices to operate properly. So the most important thing is to plan ahead because otherwise one might fall behind.