You are in the right place if you have never programmed before. This folder is your map to everything student-facing in the repository.
- Install a compiler for your operating system — follow ../docs/TOOLCHAIN.md exactly (Windows · macOS · Linux sections, ~15 min).
- Build and run your first program — the same doc, § 4–5 (~10 min).
- Read the glossary "Week 1" terms (~5 min) — these words will be used in lecture 1.
| When | What | Where |
|---|---|---|
| Before lecture | skim the week's plan | ../COURSE_SCHEDULE.md |
| In lecture | watch live coding, take state-table notes | — |
| After lecture | re-run the examples; do in-class drills again alone | ../examples/ |
| Weekly | homework exercises | ../exercises/ |
| Before quizzes/exams | review guides | ../exams/final/review_guide.md |
| I need… | Go to |
|---|---|
| The plan for this week | ../COURSE_SCHEDULE.md |
| Example programs | ../examples/ |
| Practice problems | ../exercises/ |
| Lab instructions | ../labs/ |
| Assignment specs & rubrics | ../assignments/ |
| Capstone info | ../projects/ |
| Help with an error | GETTING_HELP.md |
| Compiler setup | ../docs/TOOLCHAIN.md |
Assignments 20 % · labs 10 % · quizzes 10 % · midterm 20 % · project 20 % · final 20 % — details and the late policy in ../COURSE_OVERVIEW.md § 4.
Programming is learned by typing, breaking, and fixing, not by watching. Expect compiler errors daily in week 1 — they are normal, they are the curriculum, and reading them is skill PF-A3 (../LEARNING_OUTCOMES.md). If you are stuck more than 30 minutes on one error, stop and get help — that is the efficient move, not a failure.