VI
Mark học AIThe two-digit year bug · the world fixed it from about 1995 to 2000 · New Year's Eve 1999
Source: US Department of Commerce, "The Economics of Y2K and the Impact on the United States" (17 Nov 1999); US Senate Special Committee on the Year 2000 Technology Problem, "Y2K Aftermath – Crisis Averted" (29 Feb 2000). The full texts were blocked in the working environment and were checked through search excerpts.
Source: memory cost from the New York Review of Books, 23 Sep 1999 (secondary source); $100 billion from the US Department of Commerce (Nov 1999); the 30 June 1999 deadline from the FFIEC via FDIC letters (FIL-98-38, FIL-98-93); more than 250 glitches from the Senate report of 29 Feb 2000 as reported by CBS News (secondary source).
The world spent hundreds of billions of dollars on a single date, and then nothing happened. Was the money wasted, or was it the reason nothing happened? The short answer: mostly the second, but nobody can prove it 100%, and that is exactly what makes all prevention work hard.
The answer is Mark's assessment, based on the US Senate report (2000) and the sources in Part 9. The global "hundreds of billions" is a forecast by Gartner ($300–600 billion) and IDC ($297 billion), secondary sources.
From a memory-saving shortcut to a New Year's Eve watched hour by hour.
Source: New York Review of Books, 23 Sep 1999 (memory; secondary source); Computerworld, 6 Sep 1993 (secondary source); FDIC FIL-50-97 (9 May 1997); Executive Order 13073; S.Res.208; Public Law 105-271; FDIC FIL-98-38 and FDIC/Fed documents of Sep 1999 (99%); Federal Reserve: Special Liquidity Facility and Governor Kelley's speech of 29 Jul 1999; Commerce, 17 Nov 1999; OMB 11th quarterly report (Dec 1999); Defense Department briefing of 4 Jan 2000 via UPI and NYT (secondary source; reported duration varies from 2–3 hours to "several hours"); Senate report of 29 Feb 2000 via CBS News (secondary source); BBC, Sep 2001, via Slashdot and Computer Weekly (secondary source). Checked through search excerpts.
Seen through the eyes of the time: nobody knew how many programs would break, only that the deadline could not move.
Source: FDIC FIL-50-97, FIL-98-38, FIL-98-93; FDIC/Fed documents of Sep 1999 (99%); Senate report of 29 Feb 2000 via CBS News (no serious disruption; secondary source).
Source: Executive Order 13073 (American Presidency Project, Clinton White House archive); OMB 11th quarterly report (Dec 1999). Checked through excerpts.
Source: signing statement for S. 2392, 19 Oct 1998 (American Presidency Project); Clinton White House archive; Florida Bar Journal and FindLaw (secondary sources).
Source: Federal Reserve, Governor Kelley's speech of 29 Jul 1999; Special Liquidity Facility documents; New York Fed staff report 266 (2006). Checked through excerpts. The article does not use the figure "$50 billion in extra cash" because no source could be found.
What changed after Y2K, and one lesson the world learned backwards.
Source: FDIC FIL-50-97 (inventory by 30 Sep 1997); FFIEC statement on Y2K business risk, Dec 1997, via New York Fed circular 10958; Public Law 105-271. The 2038 date is arithmetic: 2³¹ − 1 seconds after 00:00 UTC on 1 Jan 1970. The "model for later" view is Mark's.
The most quoted lesson after Y2K was "don't panic next time". That is the wrong lesson: there was no need to panic this time because people panicked at the right moment, two years early.
The Senate report also noted something few remember: 32 countries, including Australia, the UK, Canada and Germany, reported "no incidents" to the International Y2K Cooperation Center, even though the press reported incidents in those very countries. Part of "nothing happened" came from under-reporting.
Source: Senate report of 29 Feb 2000, quoted in Deseret News, 29 Feb 2000 (secondary source). The "learned backwards" view is Mark's.
14 things often said about Y2K, checked against US government documents and clearly labelled sources. Tap a row to see why.
US Department of Commerce (17 Nov 1999): about $100 billion over 1995–2001, about $365 per American (per-person figure via Nextgov, secondary source). Computerworld (secondary) says it could reach $114 billion.
OMB 11th quarterly report (Dec 1999): $8.38 billion, fiscal years 1996–2000. GAO had a different estimate of about $8.7 billion (secondary source). Different scopes, not one wrong number.
FFIEC: critical systems tested by 30 Jun 1999; late meant "Needs Improvement", more than 30 days late could mean "Unsatisfactory" (FDIC FIL-98-93). By Sep 1999, 99% had finished.
A special liquidity facility from 1 Oct 1999 to 7 Apr 2000, priced 150 basis points above the federal funds target; a larger currency order for 1999. The often-quoted "$50 billion" could not be sourced.
Public Law 105-271, signed 19 Oct 1998. It shields information shared in good faith, but not liability for systems that actually fail.
These countries did not see more problems (National Geographic Education; Russia spent up to 100 times less than the US per Gartner via ACM TechNews; secondary sources). But dependence on computers differed, Koskinen argued US systems were more complex, and 32 countries reported "no incidents" despite press reports. No causal study exists.
Memory in 1960 cost roughly a million times more than in the late 1990s; storing two digits was a sensible saving (NYRB 1999, secondary source). The mistake was that programs lived far longer than anyone expected, and nobody fixed them once memory got cheap.
That is a late-1990s Gartner forecast, not a measurement. IDC estimated about $297 billion (1995–2001). Both are secondary sources.
"Doomsday 2000" (Computerworld, 6 Sep 1993) is the best-known warning in the press. "First" is a common label, not a proven fact.
Signed 32-bit Unix clocks overflow at 03:14:07 UTC on 19 Jan 2038 (arithmetic). The risk is real for old systems, but many have moved to 64 bits. It is too early to say it will be as big as Y2K.
The bug was real and was fixed at a cost of about $100 billion in the US. Even so, the Senate report still recorded more than 250 glitches in about 75 countries. "Nothing" was the result of the fixing, not proof there was no bug.
A ground station for a US reconnaissance satellite system failed for about 2–3 hours (Defense Department briefing, 4 Jan 2000, via UPI and NYT; secondary sources). There were also problems at a nuclear power system in Ukraine and a few 911 systems in the US (Senate report via CBS News, secondary source).
It did not happen. The Senate report: glitches were fixed quickly and none caused serious disruption.
2000 was a leap year (divisible by 400), so 29 Feb 2000 was a second test date. In Sep 2001, Northern General Hospital in Sheffield (UK) disclosed that about 150 prenatal screening results had been miscalculated because of a Y2K bug (BBC via Slashdot, Computer Weekly; secondary sources).
Source: as noted in each row; full list in Part 9.
Scores are Mark's assessment based on the sources in Part 9, not figures from a study.
Y2K was one of the most successful acts of prevention of the computer age. Its biggest weakness was not the fixing but the telling: the world could not prove its own success.
Press coverage in late 1999 included doomsday forecasts: planes falling, wide blackouts. When those did not happen, people compared the outcome with the worst forecast, not with "what if nothing had been fixed".
Some professionals had real doubts: former Pentagon CIO Paul Strassmann said "I think we have been had" (secondary source). The useful question is not "was there a bug" but "was the money well spent": many Y2K budgets also paid to replace old systems altogether.
The "More" section is Mark's commentary; Strassmann quoted from ACM TechNews, Jan 2000 (secondary source).
For any prevention work: security, backups, testing, maintenance, workplace safety.
1. The last prevention work your team did well: does anyone outside the team know what it avoided?
2. Does the team have a list of systems, accounts and contracts about to expire? Which ones are "critical"?
3. Does the next prevention milestone have an owner and a consequence if it slips?
4. If your manager asks "there were no incidents last year, why do you still need budget?", what number can you show?
5. What is your team's "2038": an expiring certificate, an unsupported library, the only person who knows a system about to leave?
Priority to documents from Congress, the White House, Commerce, OMB, the FFIEC and the Fed. The working environment blocked government sites, so the primary documents were checked through those sites' own excerpts in search results, without opening the full texts. Secondary sources are labelled.