knaxuslearn · build · ship

Roadmaps / STM32 / How the plan works

Read first

How the plan works

Time model. One study week is 8 hours: about 2 hours of reading, 5 at the bench and 1 for review. The core path is 16 weeks, 128 hours. Optional stretch work adds about 24 hours (four items of about 6 hours: the bank-swap bootloader of Phase 4, a Zephyr port of the loop, a hardware fast-off path for the stuck-loop case, and real CAN traffic), so the full path is 152 hours. Fresher pacing: plan 20 weeks (160 hours), laid out above. Before every capture, write down your prediction (the worst-case interval or latency you expect), then compare it with the capture. On the 160-hour fresher plan, allow 32 weeks at 5 hours a week and 40 at 4. Week 0 is an extra 10 hours and is optional. Practice projects are the bench time of their weeks, not extra hours.

Every phase has the same parts. A weekly table, up to three practice projects, up to five repositories to read, one milestone checkpoint, and five questions to check yourself. The checkpoint is the point of the phase; the weekly deliverables are steps toward it.

Scoring. Score each checkpoint yourself, then ask one other engineer to score it. Use six dimensions: specification and budgets; trade-offs and decisions; verification and correctness; measurement on real hardware; failure handling and safety; communication and influence. Use four levels: 1 Works on your desk; 2 Sound (specified, tested and repeatable: a stranger can rerun your captures); 3 Proven (trade-offs measured, holds at the limits, a seeded fault is caught); 4 Leading (a method other teams reuse, with a measured outcome). With no second engineer, post your hand-in on the ST Community forum, label your score "self-scored" and cap it at 2.

CheckpointJudged mainly on
1 Timing baselineMeasurement; verification
2 Control loop and RTOSSpecification; trade-offs; measurement
3 Interfaces and faultsVerification; failure handling
4 Bootloader and updateFailure handling; communication; trade-offs