Semester 0: Orientation & Foundation
Year: Pre-Engineering | Phase 0 | Weeks 4-8 | 5 weeks
This semester builds algorithm intuition, a CS mental model, and clean coding habits. Study discipline is established in Pre-Semester Launchpad.
Semester 0 is populated as a complete orientation block, including the semester project, checkpoint gate, cumulative review, and exam.
Goal
Build algorithm intuition, CS mental model, and clean coding habits so later technical semesters land on solid conceptual vocabulary and code quality standards.
Prerequisites
Requires Pre-Semester Launchpad. You should already have a working study routine, development environment, and basic Git workflow.
Phase Completion Contract
- Explain: basic algorithm growth intuition, a simple map of core CS areas, and clean code principles.
- Build: one small orientation project demonstrating algorithm visualization and clean code practices.
- Evidence: Feynman notes, tested repo with clean code, and checkpoint answers.
- Do not advance if: you cannot explain the basic CS map and algorithm intuition from memory or cannot write clean, tested code.
Modules
| # | Module | Focus |
|---|---|---|
| 1 | Module 1: Algorithm Intuition & Visualization | Grokking Algorithms - Big-O, search, graphs, and how to see algorithm state |
| 2 | Module 2: CS Fundamentals Overview | CS Distilled - breadth-first map of core CS ideas |
| 3 | Module 3: Clean Code Introduction | Clean Code - naming, functions, structure, and testing basics |
Also this semester: Semester Project · Checkpoint Gate · Cumulative Review · Semester Exam Portfolio Artifact | Common Failure Modes | Bridge Review
Core Resources
| Book | Role |
|---|---|
| Grokking Algorithms | Primary for algorithm intuition and visualization |
| CS Distilled | Primary for a compact map of computer science |
| Clean Code | Primary for naming, functions, and code hygiene |
Cross-Cutting Tracks Active This Semester
| Track | Level | Focus This Semester |
|---|---|---|
| A: Testing | Level 1 | Unit tests - every exercise and project task ends with at least one assertion or test |
| B: Git | Level 1 | Small commits, readable messages, and branch-based work |
| E: Engineering Fundamentals | Level 1 | Terminal basics, editor workflow, simple debugging, and reading technical docs without avoiding them |
Weekly Arc (5 Weeks)
| Week | Focus | Modules / Activities |
|---|---|---|
| 4 | Algorithm intuition begins | Module 1 start, visualize arrays, search, and runtime growth |
| 5 | Visual reasoning and tracing | Finish Module 1, hand-trace algorithms and write simple explanations |
| 6 | Breadth-first CS map | Module 2 start, connect hardware, software, data, networks, and systems |
| 7 | Clean code practices | Finish Module 2, start Module 3, naming, functions, and basic testing |
| 8 | Integration and assessment | Finish Module 3, build orientation project, checkpoint, review, and exam |
Deliverables Checklist
- All module warm-up quizzes attempted
- All module lessons and key concepts completed
- All code katas completed
- All retrieval practice completed for each module
- All Feynman notes written
- All spaced repetition card tables exported or transcribed
- All module quizzes completed
- Semester project completed and self-reviewed
- Checkpoint gate passed
- Cumulative review completed
- Semester exam completed
Capstone Throughline
Every semester must leave behind evidence that can survive into the final capstone defense.
- Artifact carried forward: study system baseline and onboarding reflection.
- What to preserve: Keep the learning workflow, baseline diagnostic notes, and first clean-code habits available as the setup evidence that made the later capstone sustainable.
- Module threads: Module 1: Algorithm Intuition & Visualization, Module 2: CS Fundamentals Overview, and Module 3: Clean Code.
- Defense prompt: In Semester 10, explain how this semester's artifact changed a capstone decision, reduced a risk, or made the final system easier to defend.