Skip to main content

CS & Systems Engineering Curriculum

A guide-first curriculum for self-directed computer science, systems, and software engineering study.

Beyond the core: the Advanced Engineering Path adds ten lesson studios and a maintenance residency. The resource map assigns books and papers to concrete work.

Start Here​

If you are new, use this order:

  1. Read Getting Started.
  2. Read the Confidence Contract so you know what is complete today.
  3. Use Path Levels to stay focused on the next actionable stage.
  4. Complete Pre-Semester Launchpad.
  5. Complete Semester 0 Orientation.
  6. Complete Semester 1 Mathematical & CS Foundations.
  7. Continue through Semesters 2-10 in order, using each semester's checkpoint before advancing.

What This Is​

This project is trying to teach engineering judgment, not just accumulate topics. The intended path combines:

  • computer science foundations
  • systems reasoning
  • clean implementation habits
  • architecture and operational thinking
  • artifacts that prove the work was actually done

The guide is the primary teacher. Source books are support material, not the main workload.

This is a full 96-week curriculum map. The main confidence rule is simple: use learner-ready-or-better pages as coursework and treat scaffolded or blueprint pages as planning context.

What Is Usable Today​

These areas are learner-ready today:

  • Learner-ready: Pre-Semester Launchpad and Semester 0 Orientation
  • Learner-ready: Semesters 1-3 Foundations
  • Learner-ready: Semesters 4-5 Systems
  • Learner-ready: Semesters 6-7 Architecture
  • Learner-ready: Semesters 8-10 Production and Capstone

The complete status and scope notes live in Curriculum Readiness. Learner-ready means the authored teaching path and assessments are usable; it does not mean the material has completed independent review or a learner pilot.

Why This Is Not A Generic Roadmap​

Most roadmap repos tell you what to read. This curriculum tries to define how you learn and what evidence should exist at the end.

The design priorities are:

  • guide-first teaching instead of book-dump navigation
  • module completion based on explanation, practice, and artifacts
  • semester projects, checkpoints, reviews, and exams
  • architecture and operations integrated into the long-term arc

Public Path​

Learning System​

Every learner-facing module uses the same core mechanics:

  • concept pages
  • practical exercises and katas
  • retrieval practice
  • Feynman notes
  • spaced repetition prompts
  • visible artifacts

See Learning System for the exact contract.

Quick Start​

  1. Read Getting Started.
  2. Read Confidence Contract.
  3. Choose your current Path Level.
  4. Use Execution Guide to set your weekly rhythm.
  5. Keep Progress Dashboard open as your checklist.
  6. Use Readiness before relying on any page that is not learner-ready or better.

App Surfaces​

Positioning Rule​

Treat this project as a curriculum with a public learner path. If a page is not clearly marked Learner-ready, Reviewed, or Battle-tested, do not assume it is complete coursework.