Or rather, let’s not. Hacking is bad, m’kay? But if we wanted to, it turns out it’s outrageously easy to hack medical equipment.
I’m an information technology professional by trade. My work mantra is that “no matter how bad it goes, no one dies”. It have saved me from a lot of stress, and helped me keep my cool in times of crisis. The point is that even if all the IT systems are down, the data center is on fire, and the entire development team has been abducted by aliens, no one dies. At least if the aliens are of the good, not-anal-probing kind. Sure, it’s annoying that people can’t do their work, and we might lose some money during the downtime. But people can drink coffee, chat about the incompetent IT department while the problem is being fixed. And we’ll eventually cover the financial loss, because we learn from our mistakes, and become even better at what we do.
Since IT is an important part of every industry these days, I have many choices when it comes to what domain I want to work with. Because of my work mantra, however, there are some businesses I will not to get involved with. One is control systems of any kind where a simple software bug may have disastrous consequences. Think ATC, nuclear power plants, and the like. I’d prefer not to kill scores of people because
if (x > 1) had somehow turned into
if (x > 1);. Many winters ago, I spent the better part of a workday trying to figure out a baffling bug, and the
; above was the cause. Thankfully, I wasn’t responsible for making sure airplanes don’t crash into each-other. That would have been a bad day to fly.
Another industry I gladly stay away from is medical equipment. But I would have fit right in because it turns out that many of the people working in the medical IT industry are incompetent dimwits.