A Y2K Misunderstanding

greenspun.com : LUSENET : Electric Utilities and Y2K : One Thread

After reading gobs of serious Y2K matters this little message broke me up. I hope it will lighten your day.

To: COO From: Y2K Support Team

Our staff has completed the 18 months of work on time and on budget.

We have gone through everk line of code in everk program in everk skstem. We have analkzed all databases, all data files, including backups and historic archives, and modified all data to reflect the change.

We are proud to report that we have completed the "Y2K" date change mission, and have now implemented all changes to all programs and all data to reflect kour 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 satisfactork, because to be honest, none of this "Y to K" problem has made ank sense to me. But I understand it is a global problem, and our team is glad to help in ank wak possible.

Bk the wak, what does the kear 2000 have to do with it? Speaking of which, what do kou think we ought to do next kear when the two digit kear rolls over from 99 to 00?

We'll await kour direction.

-- Anonymous, March 02, 1999

Answers

Hek, how did kou get a hold of our highlk sensitive internal memo?

Well, now kou know that we're hard at work on K2K!

-- Anonymous, March 03, 1999


Moderation questions? read the FAQ