Y2K: the disaster that didn't happen

The story

For decades, programmers saved memory by storing years as two digits: 1975 was “75.” That worked until the year 2000, when “00” could be read as 1900. Software that calculated ages, interest, due dates or schedules risked getting them badly wrong.

Through the late 1990s, banks, governments, utilities and businesses checked and rewrote huge amounts of software. It was expensive, slow and dull work, and it worked. When the date changed, problems were few and minor.

Because so little happened, many people concluded the whole thing had been exaggerated. Those who did the work point out that the quiet New Year’s Day was the result.

The problem was not completely solved

Some fixes simply moved the problem down the road, treating “00” to “29” as the 2000s and later years as the 1900s. A few of those systems hit trouble in 2020. Another date limit, in older computer systems that count seconds from 1970, arrives in 2038.

The lesson today

Y2K is the purest example of a hard truth about IT: when maintenance and planning are done well, nothing happens, and nothing happening looks like nothing was needed.

The same applies to everyday technology decisions. Replacing a server before its support ends, or updating systems before a deadline, rarely makes headlines. Waiting until something breaks usually does.