Curriculum Roadmap
This page shows the intended full curriculum arc. It is broader than the currently implemented learner path.
Phase-to-Semester Mapping
| Semester | Roadmap Phase | Weeks | Focus | Duration | Public Status |
|---|---|---|---|---|---|
| Pre-Semester | Phase 00 | 1-3 | Study systems, development environment, Git | 3 weeks | Implemented |
| 0 | Phase 0 | 4-8 | Orientation, algorithm intuition, CS mental model, clean code | 5 weeks | Implemented |
| 1 | Phase 1 | 9-20 | Mathematical and CS foundations | 12 weeks | In Progress |
| -- | Buffer | 21 | Recovery, consolidation, catch-up | 1 week | - |
| 2 | Phase 2 | 22-31 | Algorithms and data structures | 10 weeks | Blueprint |
| 3 | Phase 3 | 32-37 | Software design, refactoring, design patterns | 6 weeks | Blueprint |
| -- | Buffer | 38 | Recovery, consolidation, catch-up | 1 week | - |
| 4 | Phase 4 | 39-48 | Programming and systems foundations | 10 weeks | Blueprint |
| 5 | Phase 5 | 49-58 | Operating systems and networking | 10 weeks | Blueprint |
| -- | Buffer | 59 | Recovery, consolidation, catch-up | 1 week | - |
| 6 | Phase 6 | 60-69 | Databases and distributed systems | 10 weeks | Blueprint |
| 7 | Phase 7 | 70-75 | Software architecture, DDD, API design | 6 weeks | In Progress |
| 8 | Phase 8 | 76-83 | System design, distributed architecture, leadership | 8 weeks | Blueprint |
| 9 | Phase 9 | 84-89 | Cloud infrastructure, DevOps, modern practices | 6 weeks | Blueprint |
| -- | Buffer | 90 | Recovery, consolidation, catch-up | 1 week | - |
| 10 | Phase 10 | 91-96 | Capstone integration and specialization prep | 6 weeks | Blueprint |
Total: 96 weeks = 92 learning weeks + 4 buffer weeks
Public status reflects what is currently teachable from this repo, not what the long-term roadmap intends.
Current Public Slice
The primary learner-facing route right now is:
- Pre-Semester Launchpad
- Semester 0
- Semester 1 Module 1 exemplar
- Semester 7 Module 1 exemplar
Everything else remains roadmap context or blueprint.
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.