In 2008, famous risk analyst and systems engineer Robert N. Charette raised concerns about this troubled project. He shines a spotlight on the endemic incompetence that underlies IT disasters. After two decades of documenting software failures, as Dr. Robert Charette reminds us, a lot of us just keep repeating the same expensive errors in the practice. His observations, while sincere, point to an alarming pattern. IT staff, government reps, and corporate leaders often suffer from similar delusions when it comes to the reliability of software.
Charette, who has a 50-year professional career in the industry behind him, has long been a countervailing voice in the tech surge. He went on to write Why Software Fails in 2005, a book that dug into root causes behind software failures. Since then, he has joined The Data as their Special Projects Editor. He’s a regular columnist in IEEE Spectrum, which firmly establishes his bona fides in this emerging field.
Charette’s observations are especially disheartening in an age where software is becoming more and more essential to everyday life. He believes that the reliability standards for software overall still need to be at least equal to the expectations set for serious public utilities such as electricity.
“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 accepting AWS going down or telcos or banks going out.” – Robert N. Charette
Despite the increasing dependence on software-driven solutions, Charette notes that many organizations fail to perceive the urgency of addressing software failures. He cautions that the very nature of these failures means they are predictable and therefore preventable, but too often they still attack companies.
“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.” – Robert N. Charette
Charette’s experience goes well beyond the usual software failings. He has written on the life-and-death issues of reliability in specialized areas. When it comes to developing software for medical devices, that bar gets raised. There’s another, more important reason—one that gets to the greater concern of what happens if you fail.
“When you’re building software for medical devices, there are a lot more standards that have to be met and a lot more concern about the consequences of failure,” – Robert N. Charette
The potential implications of Charette’s findings are significant, particularly as more and more industries become dependent on complex software systems. His call to action serves as a reminder that organizations must prioritize the prevention of failures to safeguard their operations and maintain public trust.
As technology continues to evolve, the repeated mistakes highlighted by Charette may pose significant risks to businesses and consumers alike. His extensive experience and ongoing analysis of these issues underscore the need for greater awareness and proactive measures in the realm of software development.