Skip to content

Rust Mastery Blueprint-A 24-Week Master-Level Syllabus

Authoring lens: Senior Principal Systems Engineer / Rust Architect. Target outcome: A graduate of this curriculum should be capable of (a) submitting non-trivial PRs against rust-lang/rust, (b) owning a low-latency fintech matching engine or risk pipeline, or (c) writing a kernel module in rust-for-linux without supervision.

This is not a "learn Rust in N days" track. It assumes the reader is already a working software engineer who can read C, has shipped production code in some language, and is willing to read source code (LLVM, Tokio, glibc, the Rust reference) as a primary learning surface.

Repository Layout

File Purpose
00_PRELUDE_AND_PHILOSOPHY.md Why Rust; the affine type system; the cost model; reading list.
01_MONTH_FOUNDATIONS.md Weeks 1–4. Toolchain, memory layout, ownership, error model.
02_MONTH_TYPE_SYSTEM.md Weeks 5–8. Lifetimes, variance, traits, smart pointers, Drop checker.
03_MONTH_CONCURRENCY_ASYNC.md Weeks 9–12. Atomics, lock-free, Pin/Unpin, Tokio & Smol internals.
04_MONTH_UNSAFE_FFI_MACROS.md Weeks 13–16. unsafe, FFI, declarative & procedural macros.
05_MONTH_PRODUCTION_ARCHITECTURE.md Weeks 17–20. Hexagonal, zero-copy I/O, observability, testing.
06_MONTH_MASTERY_CAPSTONE.md Weeks 21–24. Custom data structures, no_std, rustc internals, capstone.
APPENDIX_A_PRODUCTION_HARDENING.md LTO, PGO, BOLT, cargo-geiger, supply chain auditing.
APPENDIX_B_DATA_STRUCTURES.md Build-from-scratch reference: B-Tree, lock-free hash map, MPSC, slab.
APPENDIX_C_CONTRIBUTING_TO_RUSTC.md The compiler pipeline; bootstrap; MIR; first PR playbook.
CAPSTONE_PROJECTS.md Three terminal projects, one per career track.

How Each Week Is Structured

Every weekly module follows the same five-section format so the reader can budget time:

  1. Conceptual Core-the why, with a mental model.
  2. Mechanical Detail-the how, down to layout and ABI where relevant.
  3. Lab-a hands-on exercise that cannot be completed without internalizing the concept.
  4. Idiomatic & Clippy Drill-read 2–3 lints, refactor a sample to silence them, understand why each lint exists.
  5. Production Hardening Slice-an LTO/PGO/cross-compile/audit micro-task that compounds across weeks.

Each week is sized for ~12–16 focused hours. Skip the labs at your peril; the labs are the curriculum.

Progression Strategy

The phases form a dependency DAG, not a linear track:

Foundations ──► Type System ──► Concurrency ──► Unsafe / FFI / Macros
       │              │                │                   │
       └──────────────┴────────┬───────┴───────────────────┘
                               ▼
                  Production Architecture
                               │
                               ▼
                   Mastery & Capstone

The Production Hardening slice is intentionally orthogonal-it accumulates a hardening/ workspace that, by week 24, is a publishable Cargo template.

Non-Goals

  • This curriculum does not cover web frameworks (Axum/Actix) as primary subjects. They appear only as integration surfaces in Month 5.
  • Game development, GUI, and WASM front-ends are out of scope. Pointers are given for the curious in 00_PRELUDE_AND_PHILOSOPHY.md.
  • "Rewrite it in Rust" advocacy is explicitly avoided; the reader should finish the program able to argue against using Rust when it is the wrong tool.

Capstone Tracks (pick one in Month 6)

  1. Compiler Track-land a non-trivial PR in rust-lang/rust (e.g., a clippy lint, a diagnostic improvement, or a small MIR transform).
  2. Fintech Track-implement a multi-asset limit-order-book matching engine with sub-microsecond p99 hot-path latency, fuzzed and verified under loom.
  3. Kernel Track-write a Rust character-device driver for rust-for-linux, complete with KUnit tests and a working out-of-tree build.

Details in CAPSTONE_PROJECTS.md.

Print this path

Want to read offline or archive? Open the printable version — every section of this path concatenated into one page, styled for paper. Use your browser's Print → Save as PDF.