knaxuslearn · build · ship

Roadmaps / C++

Programming Languages · 16 study weeks · 4 phases

C++ Roadmap Beta

C++ gives you the machine with nothing between you and your mistakes. A program can pass its tests and still crash once a week, because of a data race, a dangling reference or an allocation on a hot path. These 16 study weeks teach the object and memory model, concurrency, performance and the build, so you can say why a program is slow, why it crashed and what the fix costs. You build one library, bookd, a market-data order book and feed handler, and every phase adds a checkpoint to it. At 8 hours a week the core path is 128 hours and takes 16 weeks. At 12 hours a week it takes about 11 weeks, and at 16 hours a week about 8 weeks.

This roadmap is in beta and keeps improving over time. If you spot an error, please email your suggestions and corrections to [email protected].

Read first

  1. Phase 1 · Study weeks 1-4

    The object model, memory and undefined behaviour

    This phase makes the first checkpoint possible: a core that the sanitizers pass and that allocates nothing on the hot path.

    • 3 repos
    • Milestone checkpoint
    1. Study week 1Value categories, move semantics and copy elision8 h
    2. Study week 2Object layout, alignment and padding8 h
    3. Study week 3Sanitizers (ASan, UBSan, MSan) and what each misses8 h
    4. Study week 4Allocators and std::pmr8 h
  2. Phase 2 · Study weeks 5-8

    Concurrency and the memory model

    This phase makes the second checkpoint possible: two threads that pass messages with no race, no loss and no reordering.

    • 4 repos
    • Milestone checkpoint
    1. Study week 5Threads, mutexes and condition variables8 h
    2. Study week 6Acquire and release ordering8 h
    3. Study week 7Weak memory models and what x86 hides8 h
    4. Study week 8Thread pools and executors8 h
  3. Phase 3 · Study weeks 9-12

    Performance on real hardware

    This phase makes the third checkpoint possible: a core that meets the 5 microsecond target and shows why.

    • 3 repos
    • Milestone checkpoint
    1. Study week 9Cache lines, prefetching and branch prediction8 h
    2. Study week 10Benchmarking honestly: warm-up, spread and noise8 h
    3. Study week 11Profiling with perf and flame graphs8 h
    4. Study week 12Choosing a layout from evidence8 h
  4. Phase 4 · Study weeks 13-16

    Build, verification, interop and shipping

    This phase makes the last checkpoint possible: a library you can build anywhere, fuzz, load from another language and debug after a crash.

    • 4 repos
    • Milestone checkpoint
    1. Study week 13CMake presets and targets8 h
    2. Study week 14Fuzzing with libFuzzer8 h
    3. Study week 15A stable C ABI8 h
    4. Study week 16Crash reports and symbols8 h

Also in this roadmap