Photo: Someone Not Awful, CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0>, via Wikimedia Commons
What It Is
For decades, programmers saved precious computer memory by storing years as two digits: 1985 became "85." It worked until someone realized what would happen on January 1, 2000, when "00" might be read as 1900. Systems that calculated dates, from bank interest and payroll to power plants and air traffic control, could produce nonsense or fail outright. The problem became known as the Y2K bug, and through the late 1990s governments and businesses around the world launched a massive repair effort, checking and rewriting enormous amounts of code. In the United States alone, an estimated $100 billion was spent. When midnight arrived, almost nothing broke. Many people concluded it was all hype. Those who spent years fixing it knew otherwise: the disaster didn't happen because they prevented it.
Why It Matters
Y2K is the best example ever recorded of what IT work looks like when it succeeds: nothing happens, and nobody notices. That is the daily reality of IT support, where a good day means the network stayed up, the backups ran, and problems were caught before anyone felt them. The Y2K effort also showed the scale of what technology workers can do when they organize, and it reminds us that the quiet, unglamorous work of keeping systems running underpins everything else. For young people, it is proof that the most important work in technology is often invisible, and that invisible does not mean unimportant.
