Your Roadmap: From Zero to Trading-Network Engineer

You've just spent six lessons learning what the race is, why millionths of a second are money, and how the whole thing can explode. Now imagine standing in front of a giant wall map of everything between you and the engineer's chair: nine territories, each with its own terrain — the machines that move messages, the tricks that skip the slow parts, the clocks that keep everyone in step, the switches, the measurements, the safety systems. This lesson is that map, drawn in plain English. You'll see the whole journey in one sitting, figure out honestly where you're starting, and learn the one habit every lesson in this track runs on: try the puzzle first, read the theory second. By the end, you'll know exactly what "expert" looks like — and which territory you'll conquer first. Here's the puzzle.

Scenario. You've finished the free module — you know what the race is, why microseconds are money, and why speed needs brakes. Ahead of you lies the rest of the track: nine modules, from the anatomy of a single trade to a final capstone project. Before you go further, you need an honest answer to one question: where do you start?

Given artifacts. The nine-module map (the same map animated in S4):

Your task: (1) name the module you'd start with and write one sentence explaining why — naming a specific gap, not a vibe; (2) name the ONE habit from this lesson you'll use in every future lesson, and say what you'll concretely do differently because of it.

Workspace: analyze-and-answer — two short text boxes: your starting module + one-sentence justification, and your one habit + the concrete behavior change. Nothing is graded; the boxes record your plan before the worked answer.

Commitment ritual: below the workspace sits a checkbox — "I've attempted this challenge and thought it through." Checking it (with or without typing an answer) reveals the worked answer in S7. Honor system: the page hides the answer until you commit.

The nine-module arc, in plain English

Here is the whole track as one journey. Module 1 (free, just finished) taught you the why: what the race is, why microseconds are money, why a trading network is a private race track, and why speed without brakes is a loaded weapon.

Module 2, Tick-to-Trade Anatomy, follows a single trade from the moment a price changes to the moment your order reaches the exchange — with a stopwatch on every leg, so you learn exactly where the microseconds go. Module 3, Kernel Bypass & Userspace Networking, teaches the tricks for skipping the operating system's slow middle layers: talking to the network card directly instead of waiting in line behind every other program. Module 4, Time Synchronization, is about clocks — how thousands of computers agree on the exact time using PTP (a method for syncing clocks across a network to within billionths of a second), because you can't measure a race without synchronized stopwatches.

Module 5, Low-Latency Switching, covers the special fast intersections — network switches (boxes that forward messages between cables) built for trading instead of offices. Module 6, Market Data & Order Entry, follows the two great rivers of trading: price information flowing in, orders flowing out. Module 7, Measurement & Debugging, gives you the detective's toolkit: reading the wire, timing every stage, finding where time dies. Module 8, Trading Network Design, puts it all together into a real network blueprint — with the kill switches and circuit breakers from Lesson 6 designed in from the start, not bolted on. Module 9, Expert Scenarios & Capstone, is the proving ground: hard scenarios drawn from real incidents and a final project.

Why this matters for the challenge: your starting module is the first stop on this map whose payoff you couldn't deliver today — the worked answer shows how to pick it honestly.

What "expert" actually looks like

"Expert" is not a certificate and not a vibe. It's a checklist of things you can do. By the end of Module 9, you can: time every leg of a trade's journey and name the slowest one; look at two latency measurements and pick the link a firm would buy (you can already do this — Lesson 5); explain why the operating system slows messages down and how to skip it; read a wire capture and find where time died; design a small trading network that is fast and has a kill switch, rate limits, and measurement; and — the Lesson 6 skill — sort any incident into trigger vs. amplifiers and name the missing safeguard.

Notice what's missing from that list: memorizing product names, reciting standards, collecting vocabulary. Expertise here is measured in decisions, not definitions.

Why this matters for the challenge: "expert" is the destination on your map — your starting module is simply the first gap between here and there.

The one habit: challenge-before-theory

Every lesson in this track runs on one ritual: challenge-before-theory (attempt the puzzle before reading the theory — the struggle makes you want the explanation). You've been doing it for six lessons. The order is always the same: wrestle with the challenge (10 honest minutes, hints if you're stuck), commit with the checkbox, read the theory hungry for answers, check the worked answer, take the quiz.

This works because your brain remembers what it needed, not what it was told. Reading theory first feels productive and evaporates in a week; attempting first carves a question-shaped hole that the theory fills permanently. Skipping the challenge and scrolling to the answer is the one way to waste this track — it's like reading the last page of a mystery and calling it reading.

Why this matters for the challenge: the habit you name in your answer is this ritual, stated as a concrete behavior — "what I'll do differently" is what makes it real.

How to use the tools, labs, captures, and configs

As the track continues, lessons grow new instruments — here's what each is for. Tools (like the tick-to-trade waterfall or the timing simulator) are sandboxes: change a number, watch what happens, build intuition before theory. Labs are the challenge writ large: a broken scenario, hidden worked answer, your diagnosis. Captures teach you to read the wire — the actual messages, decoded line by line, so "the network is slow" becomes "packet 7 waited 40 microseconds in a queue." Configs are real device commands with plain-English annotations: copyable, but more importantly readable — every load-bearing line explains what breaks without it.

You don't need any of them installed. Everything runs in the page. When a lesson says "open the tool," it's a tab, not a download.

Why this matters for the challenge: knowing the instruments tells you what "starting at Module 4" actually involves — animated clocks and measurement labs, not a shopping list.

The free/paid boundary, honestly

Module 1 — the seven lessons you just finished — is free, forever. It's the why: the race, the money, the race track, the disasters, this map. Modules 2–9 are the paid track: the how. That's where you time real journeys, skip real operating-system layers, sync real clocks, and build the capstone.

Here's the honest pitch, no hype: the free module taught you to think like a trading-network engineer — averages lie, plan for the worst trip, triggers vs. amplifiers, brakes before speed. The paid modules teach you to work like one, with instruments in your hands. If the free module didn't make you curious about what's inside the machines, the paid track isn't for you — and that's fine. If it did, Lesson 8 is where the hood opens.

Why this matters for the challenge: your roadmap doesn't end at this lesson — it continues into Module 2, and S10 tells you exactly what's waiting.

• The track is nine modules: the why (Module 1) → the trade's journey (2) → the machine (3–5) → the craft (6–8) → the proving ground (9).
• "Expert" is a checklist of decisions you can make — measure it, find the biggest slice, fix it, build the brakes first — not a pile of vocabulary.
• Every lesson runs on challenge-before-theory: attempt first, theory second, worked answer last, quiz to check.
• Module 1 was the free why; Modules 2–9 are the paid how — curiosity about what's inside the machines is the admission test.
• Your starting module is the first stop whose payoff you couldn't deliver today — start at the gap, not at the beginning.

Next: The Journey of an Order: The Full Map — the free taste ends here, and the paid track begins: in Lesson 4 you traced a message's journey as a simple map, but Lesson 8 turns that map into a stopwatch-measured waterfall, timing every leg of a real trade.