Robert N. Charette is a internationally known and published risk analyst and systems engineer. For the last twenty years, he has been shining a light on the continuing challenges and dangers of failing software. It would include a wide range of tangible, measurable interests that factor into any effective software development process. The way they go about implementing sometimes speaks to these deeply ingrained fantasies. His prescient critiques of software malfeasance have appeared in many outlets, including The Atlantic and IEEE Spectrum.
In 2005, Charette published a foundational article entitled “Why Software Fails.” One objective of this work was to raise awareness of the systemic problems that result in software failures across many industries. Fast-forward almost 20 years later, and he finds that we’re doomed to repeat the same mistakes. As a consequence, many trillions of dollars are unnecessarily going to waste. His research points to a disappointing reality that the industry and governments persist in failing to respond to the obvious urgency to tackle these preventable disappointments.
Charette brings a depth of experience to the healthcare sector. He’s sounded the alarm on the increasing number of software bugs that are putting patients at risk inside their medical devices. He has called attention to the fact that more than 80 medical device recalls on average each month are triggered by issues with software. These failures not only prompt substantial financial losses, but cause immeasurable trauma and emotional pain to fallen soldiers and others in need of care including their families.
In addressing the growing lack of public tolerance for software malfunctions, Charette provides an eye-opening analogy. He states, “Software is as significant as electricity. We would never put up with electricity going out every other day, but we sure as hell have no problem having [AWS] go down.” This statement underscores a critical point: society has established a lower threshold for acceptable software performance than for other essential services, potentially jeopardizing safety and reliability.
Charette’s discussions encompass notable case studies, including the Canadian government’s Phoenix paycheck system failure, which exemplifies prolonged financial and emotional distress caused by software mishaps. He calls attention to how organizations often fail to prioritize preventive measures against software failures, stating, “The biggest tragedy is that [software failure] is for the most part predictable and avoidable. Unfortunately, most organizations don’t see preventing failure as an urgent matter, even though that view risks harming the organization and maybe even destroying it.”
His role as a Special Projects Editor has uncovered significant data regarding software failures and their impacts across various sectors. That includes a powerful commentary on the growing trend of recalls involving medical devices due to software malfunctions. These failures have impacts far worse than financial return lost. They can endanger patient safety and undermine public confidence in technology.
Charette’s honest critique of what the software industry got wrong during this fractious time rings especially true within today’s often toxic digital landscape. As organizations grapple with the complexities of technology implementation, his insights remind them of the dire consequences associated with neglecting the risks of software failure.
