The mere mention of a major software error can be terrifying for any developer, project manager, or tech leader.
The CrowdStrike, an American cybersecurity technology company, became the prime example for many coders for not messing up with codes, after a software update by the company caused the Blue Screen of Death this year.
Moreover, Microsoft provided additional details about the outage, stating that approximately 8.5 million Windows devices were affected by the damage brought about by a software update.
With this let us take a look at the biggest coding errors of all time.
1. The Mariner 1 Spacecraft, 1962
NASA launched an unmanned space mission to collect data. The plan did not work out. The Mariner 1 spacecraft had barely left from the launch center, before changing its suggested pathway towards space.
Concerned that the rocket would crash land on Earth, NASA engineers ordered it to self-destruct, and approximately 290 seconds after launch, the craft was destroyed.
According to an investigation, a very basic software error was the cause. A line of code contained an omitted hyphen, causing the spacecraft to receive the wrong guidance signals.
At the time, it was estimated that the total cost of the omission exceeded $18 million (roughly $169 million in today’s dollars).
2. The Morris Worm, 1988
As part of an experiment, a Cornell University student created a worm that spread like wildfire and crashed tens of thousands of computers, because of a coding error.
Back in those days, the computers were connected by a very early form of the internet, and this made Morris worm easily travel across all the servers.
The Morris worm was essentially the first contagious computer virus.
Today, the University of Boston has preserved the worm’s source code on a floppy disk as a museum exhibit.
3. The Millennium Bug, 2000
The infamous Y2K, also known as the Millennium Bug, caused a great deal of anxiety in the years preceding 2000. Because most computers and operating systems only used two digits to represent the year, ignoring the 19 prefix for the twentieth century, there was concern that computer systems throughout the world would not be able to cope with dates after December 31, 1999. Horrible forecasts were made regarding the failure of vital data storage, banks, airlines, and power providers. With the 00 digits, how would systems handle them?
The tepid response was “quite well, actually.” Because most systems made adjustments beforehand, the millennium bug was a bit of a non-starter and didn’t cause too many real-life problems. But throughout late 1999, the fear of the possible consequences resulted in thousands of significant expenses for emergency planning and preparations; organizations, companies, and even families braced themselves for the worst.
