Pre-Semester: Launchpad
Year: Pre-Engineering | Phase 00 | 92–138 focused hours before conditional repair; legacy weeks indicate sequence
This pre-semester develops study routines, reading and communication, a safe and recoverable digital workspace, beginner AI literacy, and essential developer tooling. It assumes no programming experience.
Pre-Semester is populated as a complete launchpad block, preparing learners for Semester 0 with proper habits, tools, and Git workflow mastery.
Goal
Build a sustainable learning process and usable technical confidence before programming. Explain your work, inspect evidence, recover a practice file, use AI with independent checks, and operate a development environment and Git workflow.
Prerequisites
Entry point. No prior experience required. This is designed as the absolute beginning of the curriculum.
Begin with Readiness and Repair. No terminal or programming experience is assumed. The diagnostic identifies computer, arithmetic, algebra and technical-reading gaps and routes you to targeted lessons. Computer, arithmetic and reading readiness are needed before Semester 00; algebra can be repaired alongside it before Semester 01.
Phase Completion Contract
- Explain: study decisions, source limitations, clear questions, saved/file state, recovery boundaries, AI evidence and authority, terminal commands and Git workflow.
- Build: small reproducible development environment with an isolated configuration fixture, working study system, and basic Git proficiency.
- Evidence: one linked packet containing study/recovery observations, setup and Git history, source audit, communication revision, actual file restore, and independently checked AI practice.
- Do not advance if: required readiness, tooling/Git, project, exam or preparation dimensions remain open. A perfect daily streak is not required; demonstrated recovery and a feasible routine are.
Start with the readiness diagnostic
For a concrete first session and a route through your first programming module, use the Beginner Pilot Guide and one shared progress record. They organize existing work and preserve actual learning evidence.
Allow about one hour for the entry diagnostic and record. Complete only the repairs you need; all four together add an estimated 11–18 focused hours. These unpiloted estimates are separate from the existing core arc. Keep a readiness record and use fresh reassessment rather than memorizing the key.
Modules
| # | Module | Focus |
|---|---|---|
| 1 | Module 1: Study Systems & Habit Formation | Feasible routines, process/learning checks and recovery; optional Atomic Habits ideas |
| 2 | Module 2: Developer Environment & Tooling | Missing Semester - shell, editor, dotfiles, command-line mastery |
| 3 | Module 3: Git Fundamentals | Version control - commits, branches, collaboration, workflow discipline |
| 4 | Module 4: Reading, Reasoning and Evidence | Meaning, source trails, quantities and qualified conclusions |
| 5 | Module 5: Communication, Help-Seeking and Feedback | Clear explanations, focused questions and visible revision |
| 6 | Module 6: Sustainable Study and Recovery | Realistic capacity, observation, interruption recovery and support |
| 7 | Module 7: Digital Systems, Safety and Recovery | File/app state, provenance, permissions and actual restoration |
| 8 | Module 8: AI for Learning and Everyday Work | No-code tutoring, independent verification, privacy and action control |
Modules 4–6 moved from Semester 00; keep equivalent completed evidence. Modules 7–8 are new clustered technical preparation. Follow the integrated route to interleave technical practice with study skills; module numbers do not impose a strict serial order. See research and resource selection for the placement rationale.
Also this Pre-Semester: Foundation Project · Checkpoint Gate · Cumulative Review · Readiness Exam Portfolio Artifact | Common Failure Modes | Bridge Review
Core Resources
| Resource | Role |
|---|---|
| Deep Work (Cal Newport) | Optional selective reading - focus and attention management |
| Atomic Habits (James Clear) | Optional selective support - habit design; local lessons teach the core route |
| Missing Semester (https://missing.csail.mit.edu/) | Selective - shell, tools and editor sections needed for Module 2; full-course completion is optional |
| Pro Git (https://git-scm.com/book) | Primary - version control fundamentals |
Cross-Cutting Tracks Active This Pre-Semester
| Track | Level | Focus This Pre-Semester |
|---|---|---|
| B: Git | Level 1 | Foundation setup - repo creation, commit discipline, basic branching |
| E: Engineering Fundamentals | Level 1 | Terminal mastery, editor configuration, dotfiles management |
Suggested sequence
Start with readiness and one realistic study calendar. Use sustainable-study observations during ordinary practice. Study digital state/trust before installing tools, then interleave environment/Git with file recovery. Practice reading and asking for help using those real artifacts, and do AI verification after the reading/arithmetic prerequisites. Finish with the project, cumulative review, checkpoint and exam.
The detailed route identifies prerequisites and evidence reuse. Plan roughly 10–14 weeks at ten focused hours per week, or 5–7 at twenty, before conditional repairs. These are provisional planning estimates, not measured beginner completion times.
Deliverables Checklist
- All module warm-up quizzes attempted
- All module quizzes completed; Module 2 at least 18/20 and Module 3 at least 21/23, alongside their required practical checks
- Selected Missing Semester material needed for Module 2 outcomes completed with hands-on practice
- Required module practice completed, with SS1–SS3, R1–R3, C1–C3, S1–S3, DS1–DS3 and AL1–AL3 all at 2/2
- Study routine documented across the core arc, including recovery from interruptions
- Computer, arithmetic and technical-reading readiness demonstrated; any algebra repair scheduled before Semester 01
- Foundation Project completed
- Checkpoint Gate completed
- Cumulative Review completed
- Readiness Exam completed
Transition To Semester 0
Upon completion of Pre-Semester Launchpad, you should have:
- sustainable study habits that can handle a multi-week technical block
- a working development environment with terminal, editor, and version control fluency
- enough Git discipline to keep later projects readable
- a repeatable planning-cycle review and recovery system
- evidence-reading and help-seeking skills, a demonstrated file restore, and an honest AI-assistance record
Begin Semester 00 with Programming Basics. Its study allowance is additional to Launchpad.
Workload and advancement contract
Use Workload and Progression for the complete hour allocation, prerequisite order, evidence reuse, score thresholds and repair rules. Its estimates do not establish learner-tested duration. All required gates apply together; conditional pass means repair remains, not permission to skip a gate.