Working in IT now, as I did back then, the great lengths we had to go to in order to make computer software that was written in the 70’s and 80’s (or older) treat 21st century dates correctly is still astounding. The whole millenium thing was so hyped up all over the world, but especially in the USA where I was working at the time.
It was as if we didn’t succeed in analysing every bit of computer software and editing thousands of lines of code in hundreds of programs, testing them thoroughly to ensure they were working, we might wake up to find it was Armageddon not the dawn of a new millenium.
In memory of all those struggles experienced by thousands of Analysts and Programmers around the world, here is a memo from 1999 that brings it all flooding back. Enjoy…
Our staff has completed the 18 months of work on time and on budget.
We have gone through every line of code in every program in every system.
We have analyzed all the databases, all the data files, including backups and historic archives, and modified all data to reflect the change as requested by management.
We are proud to report that we have completed the “Y to K” date change mission, and have now implemented all changes to all programs and all data to reflect your new standards:
Januark, Februark, March, April, Mak, June, Julk, August, September, October, November, December
as well as:
Sundak, Mondak, Tuesdak, Wednesdak, Thursdak, Fridak, Saturdak
I trust that this is satisfactory, because to be honest, none of this “Y to K” problem has made any sense to me.
But I understand it is a global problem, and our team is glad to help in any way possible.
And what does the year 2000 have to do with it?
Speaking of which, what do you think we ought to do next year when the two digit year rolls over from 99 to 00?
We will await your direction.
Image used under a Collective Commons License from https://commons.wikimedia.org/wiki/File:AS400.jpg