Y2K1
T h e Y e a r 2 0 0 0 P r o b l e m Argument for the statement "The Year 2000 bug will have such extensive repercussions that families and individuals should begin planning now for the imminent chaos." The Ticking Bomb Introduction A serious problem called the "Millennium Bug", and also known as the "Year 2000 Problem" and "Y2K", is bringing a new century celebration into a daunting nightmare. In the 1860s and 1970s, when computer systems were first built, the computer hardware, especially information storage space, was at a premium. With an effort to minimise storage costs, numeric storage spaces were drained to the smallest possible data type. Ignoring the fact that software may be run in multiple centuries, programmers started conserving storage spaces by using two digits to specify a year, rather than four. Consequently, on January 1, 2000, unless the software is corrected, most software programs with date or time may malfunction or may not recognize the entries in the year fields "00" as the year as "1900" instead of "2000" . Year 2000 problem is not restricted only to the above exigency. 20 years ago, everybody understood that a leap year came every 4th year except for every 100th year. However, a piece of algorithm
. . .
Some common words found in the essay are:
Millennium Bug, Consequently January, Driving Licence, Importantly Award, Dilemma Six-digit, Real Clock, Standish CHAOS, Hardware Dilemma, Calculated Age, Dilemma Implied, millennium bug, date fields, current date, cmos real, real clock, date birth, computer system, cmos real clock, current date birth, computer hardware, january 1, date system, date birth date, january 1 2000, date system running,
Approximate Word count = 2404
Approximate Pages = 10 (250 words per page double spaced)
|
 |
