Track 2 · Planned · Tentative Q4 2026
Deep C, Determinism & Pragmatic Standards (MISRA / CERT C)
The C failure modes that MISRA C and CERT C exist to tame, and an engineering-first way to apply both without drowning in warnings.
Track 2 isn’t on sale yet. It opens for pre-order when writing starts, with release planned for Q4 2026.
I need Track 2 sooner
Why each module matters
- 2.1The Fractured Foundation: C's Dark Corners & Undefined BehaviorLearn the exact language failure modes that safety and security standards exist to tame.
- 2.2Safety vs. Security: Pragmatic MISRA C & CERT CTurn MISRA C and CERT C from a wall of warnings into a short list of rules that matter, and learn how to justify the exceptions.
- 2.3Static Analysis Engines & The Developer Friction TaxUnderstand how static analysers work and where they stop, so tuning them saves engineering hours instead of burning them on false positives.
- 2.4The Critical Guardrails: Bounding Types, Memory & Control FlowBound types, memory and control flow so execution stays predictable on devices that run for years.
- 2.5Dynamic Analysis, Sanitizers & Runtime Bounds CheckingCatch memory corruption in automated test runs, before the code reaches customer hardware.
The cost of a single failure
- The failure it addresses
- Hours lost to false-positive static analysis warnings, and rule-breaking C that turns into field bugs.
- Typical cost if it happens
- About $15,000 in developer time lost to alert fatigue over a project.
- What the track teaches
- Teaches the few MISRA C and CERT C rules that prevent most real bugs, and how to document a justified deviation for hardware code.
Cost benchmarks and engineering labour estimates are drawn from typical industry averages (fully loaded engineering rates of $80–$100 an hour, typical prototype fabrication costs, and low-to-mid volume manufacturing runs). They are provided for risk assessment, educational planning and internal budgeting only. No specific financial return, operational saving or outcome is guaranteed. All tracks
Release emails for Track 2
One email each time a module in this track ships.
Track 2 / Module 2.1
The Fractured Foundation: C's Dark Corners & Undefined Behavior
Integer promotion, signed shifts, pointer arithmetic, type punning and sequence points on 16-bit and 32-bit targets.
- Status
- Planned
- Track release
- Q4 2026 (tentative)
- Included in
- Track 2
Path
The step-by-step path for this module is published before it’s released.
Every module includesHandbook (PDF)
Some modules also ship extra files, such as code or register maps.
Track 2 isn’t on sale yet. It opens for pre-order when writing starts, with release planned for Q4 2026.
Track 2 / Module 2.2
Safety vs. Security: Pragmatic MISRA C & CERT C
The few rules that prevent most runtime failures, the ones that hurt driver code, and how to document a deviation for a register access or a naked ISR.
- Status
- Planned
- Track release
- Q4 2026 (tentative)
- Included in
- Track 2
Path
The step-by-step path for this module is published before it’s released.
Every module includesHandbook (PDF)
Some modules also ship extra files, such as code or register maps.
Track 2 isn’t on sale yet. It opens for pre-order when writing starts, with release planned for Q4 2026.
Track 2 / Module 2.3
Static Analysis Engines & The Developer Friction Tax
Linters versus path-sensitive analysers, alert fatigue, baselining legacy code and keeping CI fast.
- Status
- Planned
- Track release
- Q4 2026 (tentative)
- Included in
- Track 2
Path
The step-by-step path for this module is published before it’s released.
Every module includesHandbook (PDF)
Some modules also ship extra files, such as code or register maps.
Track 2 isn’t on sale yet. It opens for pre-order when writing starts, with release planned for Q4 2026.
Track 2 / Module 2.4
The Critical Guardrails: Bounding Types, Memory & Control Flow
Fixed-width types, explicit casts, static pools instead of malloc, bounded recursion and exhaustive switch statements.
- Status
- Planned
- Track release
- Q4 2026 (tentative)
- Included in
- Track 2
Path
The step-by-step path for this module is published before it’s released.
Every module includesHandbook (PDF)
Some modules also ship extra files, such as code or register maps.
Track 2 isn’t on sale yet. It opens for pre-order when writing starts, with release planned for Q4 2026.
Track 2 / Module 2.5
Dynamic Analysis, Sanitizers & Runtime Bounds Checking
UBSan on target, ASan under QEMU, and an assert() that logs to non-volatile memory instead of hanging in while(1).
- Status
- Planned
- Track release
- Q4 2026 (tentative)
- Included in
- Track 2
Path
The step-by-step path for this module is published before it’s released.
Every module includesHandbook (PDF)
Some modules also ship extra files, such as code or register maps.
Track 2 isn’t on sale yet. It opens for pre-order when writing starts, with release planned for Q4 2026.