#019 – Modernizing Embedded Systems: Step #3 – Adopt DevOps

This podcast episode explores step three of modernizing embedded software development: adopting DevOps practices to solve the critical problem of late and over-budget project delivery in embedded systems. Host Jacob Beningo discusses the four core DevOps principles, presents a compelling case study of the Ariane 5 rocket failure that cost $500 million, and provides practical guidance for implementing CI/CD pipelines to improve software quality and delivery speed. Chapters: 00:00 Introduction to DevOps in Embedded Systems Modernization 02:05 The Problem: Late and Over-Budget Embedded Projects 03:00 Four Core DevOps Principles for Embedded Development 07:01 DevOps as Modern Agile Development 08:40 Understanding the DevOps Value Feedback Loop 14:04 Real-World Application: Why DevOps Matters for Embedded Developers 15:03 Case Study: The Ariane 5 Rocket Disaster 19:56 Implementing DevOps: A Phased Approach 20:46 Starting with Automated Builds and Containers 23:12 Code Quality and Standards Enforcement 25:15 Regression Testing and Artifact Management 28:05 Next Steps and Conclusion Key Takeaways: • Only 35% of embedded development teams deliver projects on time, with most running 3-6 months late • DevOps focuses on incremental value delivery, improved collaboration, automation, and continuous improvement • The Ariane 5 rocket explosion ($500 million loss) could have been prevented with proper integration testing and CI/CD practices • Start DevOps implementation with automated builds using containers to create unified development environments • Enforce code quality and standards automatically within CI/CD pipelines using tools like Misra C/C++ • Implement regression testing to catch bugs early when they're easier and less costly to fix • Use metrics analysis to automatically identify tight coupling and potential bug locations in code • Artifact management ensures traceability and ability to deliver specific software versions to customers • Deployment automation should at minimum enable automatic hardware testing, even if not direct customer deployment • DevOps creates a value feedback loop between companies and customers through observability and telemetry