knaxuslearn · build · ship

Roadmaps / Fundamentals

Foundations · 16 study weeks · 4 phases

Fundamentals Roadmap Beta

Every strong engineer meets a bug that is not in their own code. The language behaves oddly, the operating system schedules something you did not expect, or the network drops a packet at the worst moment. These 16 study weeks give you the ground underneath: how a language runs your code, what the operating system does for it, how threads and locks really behave and how TCP behaves when things go wrong. You build one system, echoq, a small message queue server, 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. At the end you can explain a slow or stuck process from evidence, not from guesses.

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

    Languages, memory and measurement

    This phase makes the first checkpoint possible: a server you can measure and a clear picture of where its memory goes.

    • 5 repos
    • Milestone checkpoint
    1. Study week 1Values, references and pointers8 h
    2. Study week 2Memory management: garbage collection, manual and ownership styles8 h
    3. Study week 3Profilers: CPU and heap8 h
    4. Study week 4Errors and how languages report them8 h
  2. Phase 2 · Study weeks 5-8

    The operating system

    This phase makes the second checkpoint possible: a server that stores data durably and where you can say what it asks of the kernel.

    • 4 repos
    • Milestone checkpoint
    1. Study week 5Processes and threads8 h
    2. Study week 6The file system and the page cache8 h
    3. Study week 7I/O models: blocking, non-blocking, epoll and iouring8 h
    4. Study week 8Observing a running process: strace, perf, /proc, iostat8 h
  3. Phase 3 · Study weeks 9-12

    Concurrency

    This phase makes the third checkpoint possible: a server that shares state across threads without races or deadlocks.

    • 4 repos
    • Milestone checkpoint
    1. Study week 9Threads, locks and condition variables8 h
    2. Study week 10Race detection: Go race detector, ThreadSanitizer, Java stress harnesses8 h
    3. Study week 11Deadlock, livelock and starvation8 h
    4. Study week 12Channels, queues and actors against shared state8 h
  4. Phase 4 · Study weeks 13-16

    Networking and failure

    This phase makes the last checkpoint possible: a server that behaves under slow clients, resets and load, and that you can explain from a capture.

    • 2 repos
    • Milestone checkpoint
    1. Study week 13TCP: handshake, windows, retransmission and congestion8 h
    2. Study week 14Framing and partial reads8 h
    3. Study week 15DNS, TLS and HTTP at the level a server engineer needs8 h
    4. Study week 16Load testing and percentiles8 h

Also in this roadmap