Failing forward
-
I have an application that runs 24x7. Prior to the new time change here in the US I updated the computer the application runs on. I verified the registry entries and following the time change checked to see that the system time was correct. I thought everything was OK until the customer reported that there was something wrong with the data coming from the application. It turns out that the application, since it was running through the time change, did not update the active time bias in memory. Before realizing the source of the error I even wrote a test using what I thought was the offending code, but it worked correctly. The fix was simple--restart the application. It is a bit annoying though to keep finding flaws that only show up because the application never stops.
>>>-----> MikeO