Summary: It was astonishing to find how unprepared the government is for this potentially devastating problem facing the American people. The government has had nearly three years of knowledge about this problem but hasn't even been able to get up to the government standards that they set back in 1996. The government is really lagging behind and could essentially destroy the American economy if they keep up the performance they are currently demonstrating. The government appears to have let the American people down. The government is now starting to realize what a dramatic effect this could have on the entire world including the US. The most powerful country may be brought to its knees because of some little flaw in writing codes for computers in the last fifty years. This microscopic line of code could inevitably destroy the entire world's economy and also possibly cause a malfunction of the world's nuclear arsenal. This could cause them to fire at will or even just detonate in their silos. Furthermore it is very critical to observe the governments efforts in trying to bring this e

To begin, here is a little information about what all of the hype is about. Arie van Deursen, of The Economist, describes what the major problem with the Y2K bug is. "The Year/2000 problem is about two-digit dates. But there is more to it. The year 2000 is a leap year; some programs know this. They check whether a year is divisible by four, and conclude that 2000 is a leap year. Or, they're more rigorous and aware of the exception: a year divisible by 100 as well is not a leap year - unless it's also divisible by 400. So neither 1900 nor 2100 are leap years - but 2000 is. Many programs, however, incorrectly treat the year 2000 as a non-leap year. This may stem from the use of two-digit dates (i.e., "00" is treated as 1900 rather than 2000). Usually, the programmer had the wrong algorithm in mind. A common error is assuming centuries are never leap years. Here, the programmer forgets the "exception to the exception." The other common error is, believing the year 2000 cannot be a leap year. This may be a result of believing leap years cannot be divisible by 1,000 (rather than 100). The leap year problem is serious. Consider the $1 million in damages caused by the failure of control computers in a New Zealand aluminum smelter. The computers could not deal with the 366th day of 1996. Similar and larger crashes are likely in 2000."(3) Duersen also talks about problems after the Year 2000 hits. "Luckily, there may be a ray of hope. For most of the systems, we have 31 + 28 = 59 extra days to solve the leap year problem; that is, assuming we have time available in those first eight weeks of the year 2000."(3) Also included is a progress chart issued by the government to chart advancement in updating and upgrading services and hardware. This chart also contains some progress figures. They claim that only fifty percent of the twenty-four agencies have completed their assessments by August 1997. They also claim that seventy percent of the total estimated cost comes from those agencies that aren't finished assessing their systems.

1. Australian Financial Review, http://www.afr.com.au/content/981130/inform/inform5.html, November 30,1998, Accessed on 12/01/98.

This program was implemented on June 9, 1997. This completely demonstrates the lack of respect the government had for this problem. As reported in The Year 2000 Journal, the author talks about the lack of interest on the part of the government. "As 2000 approaches, it will increasingly preoccupy policy makers and the public too. Because the millennium-bug problem is so trivial, senior managers have found it hard to take seriously, and politicians have found it even harder. Only two heads of government have given speeches on the subject: Britain's Tony Blair (with a sure instinct for a gap in the world market for leadership), and, more recently, Bill Clinton. The Group of Eight top industrial countries and the European heads of government both stitched a few lines on the millennium bug into communiques earlier this year. But for most politicians, the issue is barely on the radar."(2) There also are some estimates that I will include that came from the government. The government estimated in 1995 that to get all of the government computers to be Y2K compliant it would cost $20 billion. In 1996 the number doubled to more than $40 billion. However in 1997, now that the government understands all of the things that must be accomplished, the estimate ballooned to a number between $1.3 to $1.6 trillion! This is just one more example of the mass underestimation of the problem on the entire government's part.

My method of data collection was very limited. I was stuck using only the Internet and other on-line journals. This was very efficient because they were free and I could access them any time of the day. I also was required to subscribe to several mailing lists and e-mail newsletters. I used the Houston Business Journal, T

Some common words found in the essay are:
Deursen Economist, Bug Summary, Agency October, Clinton Eight, Ullrich September, Sampson Economist, Financial Review, Horn HCFA, John Koskinen, Services State, y2k compliant, nuclear weapons, financial review, 2000 leap, australian financial, accessed 11/02/98, australian financial review, 2000 journal, oct 26-nov 2, mission critical, health human, 26-nov 2 accessed, computer systems, http//wwweconomistcom/editorial/freeforall/19-9-98/index_surveyhtml oct 26-nov, economist http//wwweconomistcom/editorial/freeforall/19-9-98/index_surveyhtml oct,
Approximate Word count = 2644
Approximate Pages = 11 (250 words per page double spaced)