Unlock Embedded Excellence: Reliability Secrets Revealed!
summary
Describes a programmatic move to product-first embedded engineering: containerized dev with Docker and packaged releases via snapcraft, CI that runs valgrind and SonarQube linting, unit testing with GTest and Azure DevOps pipelines, plus sanity checks for consumed artifacts. Results claim defect escape at L4 drops from 70% to <20%, story cycle time halves and time-to-market falls ~30%. Observability uses traces, logs and metrics to link versions to field failures.
AI-written summary · about
chapters (8)
- 0:00Embedded reliability challenges
- 3:14Why embedded reliability matters
- 11:17People process technology framework
- 15:32Distributed embedded teams
- 22:17Reliability improvement outcomes
- 26:30Observability in embedded devices
- 28:39Engineering effectiveness summary
- 31:48Conclusion & Q&A
related talks
18mYour Toolchain is Production: The Case for Observability
54mUnraveling the Differences
01h 00mDeep Dive: Self-driving Pipelines: Building the Unbreakable Continuous...
26mDevOps Insights for the Executable Digital Twin
37mContinuous Delivery for Embedded Systems
46mFull Court Quality: Lacing Up for Speed, Stability & Style
18mEdge Intelligence: Real-Time Analytics at the Source
27mHow We Streamlined Our SDLC with Observability - from GitHUB via Jenkins, Harbor, Argo to K8S