Originally Posted by JohnHarris
I saw their thinking and action plans on the ' Millenium bug'


The Y2K problem was very real, and required an awful lot of behind the scenes work to fix. We knew about it for decades, I was a software developer in the 1980s and often had to deal with code written back in the 1970's that frequently had comments like "NB, this bit won't work in the next century" or variations thereof. The thing was back then people would write code fully expecting it to be rewritten or refactored way before the risk became an actual issue, and back then there was a very real need to save every possible byte of machine space.

All through the 1990s organisations with large legacy systems spent many tens of thousands of analyst hours trawling back though old code identifying and fixing problems so that the systems would carry on working successfully. I did practically nothing else from 1995 to 1998 except redesign databases to be Y2K compliant, and converting and migrating the data to the new design. Thanks to all the work our team, and the equivalent teams in thousands of organisations worldwide, there were no problems as we switched over. Our organisation didn't even need to put any special measures in place as we'd spent years doing the analysis, modifications and testing so we were sure it would be ok.

The media, for reasons best known to themselves, decided to trumpet this as "See? There wasn't an issue after all!" rather than "Bloody hell, those people did a good job, didn't they?"


Tim H.
1986 4/4 VVTi Sport, 2002 LR Defender, 2022 Mini Cooper SE