Roadmaps / 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. Optional stretch work adds about 18 hours (three items of about 6 hours: a second hardening pass to exposure 1.5 or lower, a cgroup-aware load test of systemd-oomd, and a bpftrace tool of your own), so the full path is 146 hours. 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 on a real host; failure handling and safety; communication and influence. Use four levels: 1 Works on your VM; 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 a Linux forum or study group, label your score "self-scored" and cap it at 2.
| Checkpoint | Judged mainly on |
|---|---|
| 1 Service and sandbox | Specification; failure handling |
| 2 Limits and resources | Measurement; trade-offs |
| 3 Network and security | Verification; failure handling |
| 4 Incident game and operations | Failure handling; communication; trade-offs |