For those who programmed in the late 1990s, Y2K was crucial. Literally: Y2K = Year 2000 .
Software that was not compatible with Y2K, apparently, included software that stored the year digits as two digits (often to save storage space) and therefore would equate 2000 to the year 1900. However, some software products for other reasons did not meet the Y2K requirements because they made incorrect date calculations for dates in the 21st and subsequent centuries.
In the last category, I had one product that I supported at a time when I had to fix it because he did not recognize the year 2000 as a leap year. Since this software controlled the automatic control system at the factory, it would have damaged some expensive components if it had not been fixed before the end of February 2000.
There were some apocalyptic forecasts that January 1, 2000 would be very bad due to software crashes due to a mismatch in 2000, and many people โdelayedโ it at midnight on December 31, 1999 for this reason. After that, many argue that forecasts were exaggerated. In my opinion, there were few problems, because many programmers worked very hard and for a long time in the late 1990s specifically to deal with the threat of problems in 2000, and they would not have done this if there werenโt legitimate concerns about the potential very bad results.
source share