The path to excellence

Goal

A comprehensive, honest program from strong developer to full-stack engineer, architect, and technical lead — built entirely from this knowledge base, so every claim in it is backed by a concept note and proven by an exercise with acceptance checks. This is the path of paths: its modules are the nine constituent paths, sequenced into five stages. It is a multi-year program by design; the unit of progress is a module inside a constituent path, tracked in todos/ and journal/, never here.

Three doctrines govern the whole curriculum:

1. Read, then build, then argue. Every module pairs concepts with an exercise and a proof; a module without a produced artifact (code, measurement, or written position) is not done.
2. One build at a time. Paths may interleave, but at most one flagship exercise is active at once — half-finished builds teach half-truths.
3. The algorithms track never stops. The interview-prep track's spaced re-solves run in the background through every stage.

Modules

Stage 1 — Foundations

• Do: Foundations — the machine and the toolkit, in full.
• Proof: its six modules' proofs; the background algorithms track started.
• Everything else stands on this. Do not skip it because it looks beneath you; the exercises will locate the gaps regardless.

Stage 2 — Craft

• Do: Software craft — design in the small and Language craft — mastery in depth, interleaved (a craft kata makes an excellent palate cleanser between language deep-dives).
• Proof: both paths' proofs; the four flagship language builds done to their acceptance bars.
• This stage forms the judgment every later stage spends.

Stage 3 — The product

• Do: The full-stack web, with Security — the defensive craft modules 1–2 woven in as its frontend and auth modules come up.
• Proof: the RealWorld capstone shipped through all five milestones.
• This is where the "full-stack" in the target title is earned end to end.

Stage 4 — Scale

• Do: Systems at scale — distributed systems & data and Platform & production, interleaved (design a thing, then learn to run it); security modules 3–6 complete here.
• Proof: both paths' proofs — the storage/cache/consensus builds and the hand-assembled platform underneath them.
• This is where the "architect" in the target title becomes credible.

Stage 5 — Multiplication

• Do: Architect & lead — the force-multiplier track, begun as early as Stage 3 supplies real material and completed here; AI engineering — the new tooling alongside.
• Proof: both paths' proofs — the strategy documents, the debt workout, the agent and RAG builds with green evals.
• The summit: the group is better because you're in it, and the tooling multiplies everything below.

Related

• Constituent paths: Foundations · Language craft · Software craft · The full-stack web · Systems at scale · Platform & production · Security · AI engineering · Architect & lead.
• The bundle's themes — the library this curriculum is a trail through.