This month, each day, except the four Sundays, I will be blogging about interesting features associated with Bengaluru, formerly known as Bangalore, as part of the Blogging from A to Z April Challenge
Remember the madness, 21 years ago?
For the uninitiated, we are referring to the presumed computer glitch that sent the world into a tizzy in the run-up to the dawn of 2000.
The fear was that everything that is connected to a network of computers -- like banks, flight schedules, even actual flights, railway networks, all types of factory operations, telecom networks, etc. -- would grind to a halt immediately after the midnight of December 31, 1999.
The basis for this fear was that in computer programs, the year was represented by the last two digits. Like, 94 for 1994, 99 for 1999 etc. When the new millennium would dawn, after 99 it would be 00. Computers, it was feared, would read it as the year 1900. And also, 00 is not one more than 99, and that would disrupt all calendar-related operations.
There were many other software-related issues too. And all those gave rise to a huge global industry trying to reformat dates and calendar data.
An electronic signboard in France incorrectly displaying 2000 as 1900 Courtesy: Bug de l'an 2000 |
Companies in the US and Europe turned to India, and in a way that set the stage for the BPO (business process outsourcing) industry.
"Besides the war room in Bangalore, Infosys set up similar Y2K rooms in Fremont, Calif., and Boston and posted coordinators in Europe and Japan to resolve Y2K issues sent to Infosys by its clients," says this article in Computer World.
According to this paper by Devesh Kapur and Ravi Ramamurti, "By 2000, India's software sector's output had grown to $8 billion and exports had risen to $6.2billion ... The US accounted for nearly 60% of India's software exports, followed by Europe with 23.5% and Japan with just 3.5%."
Of course, nothing of those fears came true. Though there might have been a few cases of not much significance where computers miscalculated the date change.
(Tomorrow, the last post in this series)