Roadmaps / Embedded Linux / 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 terminal and 1 for review. The core path is 16 weeks, 128 hours. Builds run while you read, so the plan counts your attention, not the build time; the first clean build can take several hours on a laptop (measure yours in Week 1 and plan around it). Optional stretch work adds about 18 hours (three items of about 6 hours: verified boot with signed U-Boot images, a Buildroot build of the same product for comparison, and a run of Checkpoint 3 on a real board if you own one). The full path is 146 hours. Checkpoint weeks are tight: write each ADR when you make the decision (about 20 minutes each) and script every capture. Weeks 3, 7 and 16 are the densest: at 5 hours a week plan a spill week for each. Week 0 is an extra 8 hours and is optional. Checkpoint weeks (4, 8, 12 and 16) each hold a whole checkpoint, so take two sittings: build, then capture. Predict before you measure: before every capture, write down the number you expect, then compare. Practice projects are the terminal 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; failure handling and safety; communication and influence. Use four levels: 1 Works on your machine; 2 Sound (specified, scripted 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 in an embedded Linux study group or forum, label your score "self-scored" and cap it at 2.
| Checkpoint | Judged mainly on |
|---|---|
| 1 Reproducible image | Specification; verification |
| 2 Kernel and device tree | Measurement; trade-offs |
| 3 Safe updates | Failure handling; verification |
| 4 Release and compliance | Communication; failure handling; trade-offs |