December 31, 1999

Y2K millennium rollover passes with minimal failures

As clocks rolled from December 31, 1999 to January 1, 2000, decades of Y2K remediation paid off — critical systems worldwide kept running with only scattered glitches.

What it was for

Year 2000 problemGovernments and enterprises had spent an estimated $300–600 billion rewriting COBOLCommon Business-Oriented Language — a language designed for business data processing on mainframes. date fields, testing firmwareSoftware stored in hardware that controls a device — persists across reboots and updates infrequently., and stockpiling diesel generators. The anticlimactic rollover validated ITInformation technology — the use of computers, networks, and software in organizations. project management at scale and reminded developers that legacy code outlives its authors — a lesson repeated with IPv4Internet Protocol version 4 — the 32-bit address scheme still widely used on the internet. exhaustion and mainframeA large, powerful computer for centralized organizational workloads — dominated enterprise computing before PCs. migrations.

Why it's here

Y2K was the largest coordinated software remediation effort in history.

Why it mattered

It proved enterprises could mobilize massive testing and code-rewrite programs under deadline pressure.

What it solved

Two-digit year fields in legacy systems threatened incorrect dates in finance, utilities, and embedded firmwareSoftware stored in hardware that controls a device — persists across reboots and updates infrequently..

Media

  • Year 2000 problem
    ImageYear 2000 problem

    Bug de l'an 2000, CC BY-SA 3.0, via Wikimedia Commons

Related