When Software Bugs Are Literally Fatal

A Bug in the Boeing 787 software requires a reboot every month or total loss of plane control — why is it so hard to write bug-free code?

Photo by Dion Tavenier on Unsplash

Boeing is just one example of a firm under fire due to software defects that at least partly caused lives to be lost. They aren’t alone — there is a history of high-impact software failures from today’s 737-MAX and 787 glitches to the Therac-25 defect decades ago that roasted patients alive at the doctor’s office. This article explores software testing and why it remains so difficult to get right.

Some real and anecdotal defects:

• The Boeing 787 has a rumored integer overflow date/time counter such that the FAA requires the system to be rebooted every 51 days to prevent total loss of control.
• If you ever call customer service or the IT helpdesk about any piece of software the service rep will always start with “please restart the application”, then “please restart windows”, then “please power cycle”.
• Microsoft Windows announced a 20-year-old critical “CTF” security bug a few years ago. I can’t imagine how many other bugs exist.
• My home Wifi router slows to a halt every few months. I restart it and it…