Definitions:
Discussion Forums:
News on Year 2000:
|
What is it? The Warnings
Incidents So Far:
Bad Dates:
What is your computer's "time horizon to failure" in forecasting or processing future dates?
So What? Possible Impacts:
“If it ain't broken, it's obsolete.”
|
Y2K Theme Song: Two Digits for a Date
(to the tune of “Gilligan's Island,” more or less)
—Author Unknown
Just sit right back and you'll hear a tale Of the doom that is our fate. That started when programmers used Two digits for a date. Two digits for a date. Main memory was smaller then; Hard disks were smaller, too. "Four digits are extravagant, So let's get by with two. So let's get by with two." "This works through 1999," The programmers did say. "Unless we rewrite before that It all will go away. It all will go away." But Management had not a clue: "It works fine now, you bet! A rewrite is a straight expense; We won't do it just yet. We won't do it just yet." Now when 2000 rolls around It all goes straight to @#%&, For zero's less than ninety-nine, As anyone can tell. As anyone can tell. The mail won't bring your pension check It won't be sent to you When you're no longer sixty-eight, But minus thirty-two. But minus thirty-two. The problems we're about to face Are frightening, for sure. And reading every line of code's The only certain cure. The only certain cure. [key change, big finish] There's not much time, There's too much code. (And COBOL-coders, few) When the century is finished with, We may be finished, too. We may be finished, too. Eight thousand years from now I hope That things weren't left too late, And people aren't then lamenting Four digits for a date. Four digits for a date. |
What Can Be Done? Methodologies:
The U.S. G.A.O.'s excellent in-depth description of their
Best Practices  breaks the Year 2000 job
into phases:
|
"the most important determinant of success will be how well each organization is able to prioritize the software that should be fixed firxt, so that any programs that are not fixed int time will have the smallest possible likelihood of causing serious damage or disruption." —Keith Jones, in Year 2000 Software Crisis: Solutions for IBM Legacy Systems, p. xxii
ADVICE: |
| Your first name: Your family name: Your location (city, country): Your Email address: |
Top of Page 
Thank you! | |||
Year 2000
Definitions
Radio reports on Y2K
