As the clock ticked toward midnight on December 31, 1999, people around the world were not only wondering how to celebrate. They were wondering whether the lights would stay on. Warnings had spread for years that computers might fail at the start of the year 2000. The problem even had a nickname: Y2K, short for "year two thousand."
The trouble began decades earlier. In the early days of computing, memory and storage were costly and limited. To save space, many programmers stored years with just two digits, writing 99 for 1999. That worked fine until the year turned over. A computer reading "00" might decide it meant 1900 instead of 2000, and then calculate wrong ages, dates and deadlines. A few computer scientists, including Robert Bemer, warned about the shortcut as early as the 1960s and 1970s, but most businesses chose to save money in the short term.
By the 1990s, the danger seemed real. Computers were no longer used only for math; they ran banks, airlines, power systems and government offices. A 1993 article in a computer magazine called "Doomsday 2000" helped alarm the public. In 1998, the United States government created a council to help organizations get ready, and key parts of the economy were expected to be prepared by August 31, 1999.
Fixing the problem was slow, boring and enormously expensive. Programmers had to search through millions of lines of code, often written in old programming languages, to find every place a date was used. One common repair, called windowing, taught the computer to treat small two-digit years, for example 00 through 29, as years in the 2000s. Estimates of the total bill reach into the hundreds of billions of dollars worldwide, with the United States alone spending about $100 billion.
Then January 1, 2000, arrived, and almost nothing happened. There were small glitches. Some records listed newborn babies as born in 1900, and a few systems made errors. But there were no widespread blackouts, no falling airplanes and no frozen banks. Many people decided the whole thing had been a false alarm.
The truth is more interesting. Preventing a problem has a strange side effect: when it works, nobody sees the disaster that was avoided. Experts still debate how much of the spending was truly needed. Yet many of the programmers who did the repairs argue that the quiet new year was exactly the result of their work. Y2K is remembered as a lesson that a calm outcome can be a sign of success, not of wasted effort.