Coding Guidelines – to Comply or Not Comply – Some Myth Busting
summary
Argues that coding guidelines bring measurable safety and review-time benefits but must be applied with common sense, not blindly: static tools like cppcheck and Coverity plus GCC -Werror catch many defects, but some MISRA rules (e.g., nested-comment flagging URLs, mandatory breaks) produce false positives. Recommends documenting and approving deviations, storing rationale in code and tickets, adding checks in CI or pre-commit, and rolling rules into old projects incrementally (quality weeks, only new commits enforced); real-world firmware example shows this approach prevents regressions.
AI-written summary · about
chapters (6)
- 0:00Coding guidelines debate
- 3:37What guidelines are for
- 14:12Choosing guidelines
- 22:47Guideline deviations
- 33:48Common sense approach
- 35:34Q&A
related talks
50mCore and other guidelines. The good, the bad, the... questionable?
55mC++ Core and Other C++ Guidelines - The Good, the Bad, the… Questionable?
01h 02mA Critical Look at the Coding Standards Landscape
25mBest Practices for Writing Clean and Maintainable Codes
01h 01mSome Programming Myths Revisited
55mIdentifying Common Code Smells (In C++)
30mDoes Your Code Hurt?
01h 29mC++ Core Guidelines - Modernize your C++ Code Base