Functional safety: best reliability practices and worst automotive requirements

The issue of quality software is always relevant. One way to describe fault-tolerant, reliable "no-fail" software is through standards from the automotive field, such as ISO 26262. There are techniques that help to write clearer code (security programming), subsets of language (MISRA, AUTOSAR), architectural approaches (error handling, fault tolerance), and even formal verification, as the cherry on the cake. In the report, we'll touch on applicability issues. Let's talk about code metrics, linters, and patterns.