I still remember Y2K like yesterday. I was set to graduate from college during that year. Will the airplanes just fall down from the sky? Will computers go up in frame and explored? Will software failures bring down the internet and disrupt all communications? There were so many uncertainties during the end of 1999 going into 2000. Despite all of the preparations towards the end of 1999 that every companies scrambled to ensure that their system will be ok, nobody really knew what actually was going to happen when the clock hits 01/01/2000 resetting the last two digits of the year to “00”.
There were many jobs created specializing in preventing Y2K meltdown. Luckily, that was one of my assignment during a co-op job so I got to experience that first hand. It was not fun having to comb though many lines of codes and logic to see whether or not the full four digit notations of the year are used. Unfortunately, I discovered many. Back in the days, software developers tended to short cut things and only make use of the last two digits of the year for many of the comparison logic inadvertently. It was very obvious that those logic will fail when it comes to comparing “99” with “00”. With that I could only hope that every companies discover, fix, and deploy these logic in their software before the clock hits the New Year day of 2000.
As the days got closer to 01/01/2000, the news and media’s hype around Y2K meltdown grew more worried. News about a bug in a software caused an airplane to clash in the past. But, time was not going to stop for anybody and we eventually had to face Y2K whether we were ready or not. After the ball dropped from Time Square in NY like many years before, I was relieved that no many catastrophes had happened. There were no planes fell from the sky, no computer grids meltdown! People definitely learned a hard lesson and hope not to repeat it when the next century rolls around.