Reason: Removed "And we all remember how Y2K turned out. " since the implication is that there were no problems associated with Y2k.

There were problems worldwide, just not armagedon scale, so they had minor media coverage. They were disruption to business and service issues.

Secondly, as someone who had responsibility for Y2k compliance at a financial institution in 1999, i know the amount of time and effort that was put in to fixing problems ahead of time. Cobol and Fortran programmers were dug out of their graves to fix date sensitive systems and were all very busy for a couple of years ahead of the date change. This prevented many problems.

The problem with the clock change is that it has not had wide publicity in advance, and so could adversely affect big time sensitive systems. Small systems that are not time sensitive (such as everyday office systems) will not be the issue, since clocks can be changed manually. It will be systems where automation relies on timing over the midnight period.

Another difference between this and Y2K is that Y2K highlighted flaws in coding, and changing system dates was not an option; code needed to be able to handle 00, and many programs could not.

with the time change, problems can be resolved by a single clock change, so for example for an office that is not 24/7, admins can change the time before users arrive. but for systems that are 24/7 with actions that respond to time prompts, making sure those systems turn over at the right moment will be critical.

Excellent points, Jennycouncil. Thank you!