Curriculum Roadmap
This page shows the long-range curriculum sequence.
If you are starting now, read Path Levels first. The roadmap is the long-range map; it is not the first workload.
Canonical semester readiness lives in Curriculum Readiness. Use that page before treating any semester as coursework.
Phase-to-Semester Mapping
| Semester | Roadmap Phase | Weeks | Focus | Duration |
|---|---|---|---|---|
| Pre-Semester | Phase 00 | 1-3 | Study systems, development environment, Git | 3 weeks |
| 0 | Phase 0 | 4-8 | Orientation, algorithm intuition, CS mental model, clean code | 5 weeks |
| 1 | Phase 1 | 9-20 | Mathematical and CS foundations | 12 weeks |
| -- | Buffer | 21 | Recovery, consolidation, catch-up | 1 week |
| 2 | Phase 2 | 22-31 | Algorithms and data structures | 10 weeks |
| 3 | Phase 3 | 32-37 | Software design, refactoring, design patterns | 6 weeks |
| -- | Buffer | 38 | Recovery, consolidation, catch-up | 1 week |
| 4 | Phase 4 | 39-48 | Programming and systems foundations | 10 weeks |
| 5 | Phase 5 | 49-58 | Operating systems and networking | 10 weeks |
| -- | Buffer | 59 | Recovery, consolidation, catch-up | 1 week |
| 6 | Phase 6 | 60-69 | Databases and distributed systems | 10 weeks |
| 7 | Phase 7 | 70-75 | Software architecture, DDD, API design | 6 weeks |
| 8 | Phase 8 | 76-83 | System design, distributed architecture, leadership | 8 weeks |
| 9 | Phase 9 | 84-89 | Cloud infrastructure, DevOps, modern practices | 6 weeks |
| -- | Buffer | 90 | Recovery, consolidation, catch-up | 1 week |
| 10 | Phase 10 | 91-96 | Capstone integration and specialization prep | 6 weeks |
Total: 96 weeks = 92 learning weeks + 4 buffer weeks
Readiness is intentionally not duplicated here. See Curriculum Readiness for the current canonical status of each semester.
Current Public Path
The learner-facing route is:
- Pre-Semester Launchpad
- Semesters 0-10, in order, when their readiness status supports coursework use
Use the buffer weeks as recovery and consolidation checkpoints rather than skipping them; the later semesters assume the earlier project and review artifacts exist.
Visual Curriculum Progression
Cross-Cutting Track Activation Timeline
Buffer Weeks
Four dedicated buffer weeks at natural transition points keep the plan survivable over 96 weeks.
Use them to:
- finish overdue work
- re-pass weak checkpoints
- clean notes, repos, and decks
- reduce fatigue before the next phase
Structural Milestones
- By the end of Semester 3, the learner should have one primary language, clean Git habits, and recurring engineering artifacts in writing.
- By the end of Semester 5, the learner should have completed one small real deployment rather than waiting for the cloud semester.
- From Semester 6 onward, major projects should include formal design artifacts such as ADRs, architecture diagrams, threat models, or runbooks.
- Across the whole curriculum, AI use should leave verification evidence: tests, review notes, debugging logs, or written critiques. See AI-Era Engineering.