Skip to main content icon/video/no-internet

Months before the close of the 20th century and the beginning of the 21st, much attention was paid to what was termed the Y2K Bug. Y2K is a “numeronym” denoting the year (Y) and the rollover into the new century, two thousand (2k). The perceived “bug” represented a problem in computer programming: computers, which had been operating with a simple date identification program beginning with “19” and ending in the last two digits of that year (for example, 19 [representing the 20th century] together with the year, 1998 [written as 98]), were expected to malfunction as computers made the switch out of the 20th century and into the 21st century.

The problem was conceptualized as significant and was perceived to be a widespread and global issue, as computer programmers and others who worked in industries that relied heavily on computers (e.g., banks, hospitals, stock market) worried that there would be a global shutdown as computers made the rollover transition from dates beginning with “19” into dates beginning with “20.” Further, significant concern arose about data processing capabilities when the previous two-digit dating system became obsolete and it became necessary for a four-digit dating system to come into existence. Given this valid concern on the part of programmers and business owners and operators alike, it became clear that the Y2K issue was one that could not be ignored, as potential simple programming glitches were increasingly being identified as preparations to move into a new computer dating system came into fruition.

Mitigation

Computer programmers expended extensive time and effort attempting to forecast potential Y2K bugs in then-current programming and sought to send out “patches” to various businesses and organizations in an attempt to fix any potential issues or problems as the transition was made out of 1999 into 2000. Notably, it became clear that some programmers had failed to take leap years into account when designing their time and date systems in several computer programs. This problem forced companies and organizations around the globe to check and upgrade their computer systems prior to January 1, 2000—some programmers had misunderstood that although years evenly divisible by 100 are not leap years, those divisible by 400 are leap years: 2000 was a leap year. Recognizing that there were likely to be issues with the computer dating systems, and anticipating major malfunctions if the computers were not patched properly, computer programmers sought to identify potential problems and computer clients early on and worked ardently to create the necessary fixes so as to permit as seamless a transition as possible into the new century.

Because computer programmers were proactive in attempting to develop the necessary patches to ensure a smooth computer-based transition into the 21st century, the anticipated problems (non-functioning ATM machines, glitches in air traffic control, problems with monitoring of critical care patients in hospitals, etc.) were limited. These remedial efforts on the part of computer programmers limited significantly the number of problems associated with the Y2K bug.

Legitimate or Overblown Concern?

Was it necessary for there to be such exaggerated concern over the potential Y2K bug, or did the concern itself propel computer programmers into attempting to solve computer glitches before they occurred to mitigate the potential for severe issues and complete computer shutdowns? Because many computer programs stored information using only the last two digits of the year (e.g., 1989 would be stored as 89), legitimate concern arose that computers would begin to represent incorrect dates, thereby wreaking havoc on the generation and maintenance of valuable computer data and potentially causing a complete shutdown of a computer system.

...

  • Loading...
locked icon

Sign in to access this content

Get a 30 day FREE TRIAL

  • Watch videos from a variety of sources bringing classroom topics to life
  • Read modern, diverse business cases
  • Explore hundreds of books and reference titles

Sage Recommends

We found other relevant content for you on other Sage platforms.

Loading