How Much Are You Willing to Pay for Bad Software?

Send us Fan MailWith time to market pressures constantly increasing, technology organizations are moving away from traditional waterfall development workflows and towards Agile/DevOps software development practices. Originally introduced in enterprise, IT, and data center contexts, these methodologies have made their way into embedded engineering organizations, but at the potential expense of software quality. Can embedded tech companies, especially safety- and security-critical ones, afford to sacrifice quality for speed? Brandon and Rich debate.Later, the Insiders are joined by Yannick Moy of AdaCore to discuss how the MISRA C coding standard, which was originally developed in 1998, is holding up given the complete overhaul of automotive (and other) technology stacks since the standard’s inception. Is C, a notoriously compliance-challenged language, still the best bet for safety-critical systems that are now operating alongside a host of other connected applications?Finally, Perry Cohen looks into the true cost of bad software in this week’s Tech Market Madness. After reviewing Herb Krasner’s “The Cost of Poor Software Quality in the U.S.: A 2020 Report,” he finds out just how much defunct software projects, bad legacy code, and operational software failures set back the industry, and considers how DevQualOps could help recoup some of those losses while maintaining time to market. For more information, visit embeddedcomputing.com