Most of us who are NOT the morning people know exactly how it feels like getting up an hour early and driving to work, and even worse this year it came three weeks early. Well, this change in DST has definitely affected the morning people, but for software developers and architects like me, it means another round of potential bug problem, a micro Y2K. This time it might not be as widespread, however, it’s definitely something that can’t be ignored. Last couple months at work we have started seeing potential problem with this; systems/applications that used UTC or disjoint system were problem. Most of the applications that we built we tested for this problem and have rectified it. So is your system prepared for it?
What I have seen mostly is that system that span across multiple client/servers, or systems that use heavy datetime conversion (UTC/Local) might be affected. Simply applying windows patch or available applications patches might not help, so at least get your system tested, before you start getting the support calls.