Not as good as the "Jump to Conclusions Mat", but very nearly...
For all those who have been working diligently to assure that this "economizing measure" was seamlessly implemented, these last 8 to 10 days have been a nightmare. The impact of this arbitrary change (which was two years in the planning, I understand) was minimized...IT professionals who maintain network functionality and collaborative services have been scrambling to assure that their users lives were only mildly inconvenienced as the clocks associated with every piece of technical equipment they use were adjusted forward one hour, three weeks earlier than their operating systems were pre-programmed to change.
A testimonial to the frustration level of IT professionals can be observed in the exchanges on the very generously made available Microsoft Business Solutions "Community Chat Room", where experts are accessible through live chat session to answer questions about the deployment, problems and solutions associated with the early time adjustment. Hopefully, the change that will take place in October has already been bundled into the patches we all were frantically installing network wide...it would be absolutely ridiculous to have to do this again in the fall....so of course if the warped logic of this follows, we most likely have that to look forward to....
The "good thing" (if there is anything good about it) is that in three weeks, even if you resist assimilation and do nothing at all to your computer, your machine will be in compliance with daylight savings time....however, in those three weeks, you will make yourself a royal pain in the arse for every person you collaborate with, skewing all the time stamping of documents and appointments that come from you so that they are not accurate for users who HAVE installed the patch correctly....
Hopefully, you are all set with your own DST adjustment; if not I encourage you to take care of it, both for your own computer's accuracy and for the good of the "collective".... ;-)
