One page per class, newest at the top of your teacher’s list: the agenda we followed and anything to do before next time. Away? Start here, run the warm-up yourself, and attempt the build before reading anything about it — the page holds the plan, but the ideas earn their names in the room.
Our semester runs in four units:
- Unit 1 — Objects and the Shape of a Problem: a program nobody in this room wrote, classes, methods, and encapsulation, ending in The Model.
- Unit 2 — Data Structures: the container that was wrong, dictionaries, stacks, queues, and recursion, ending in The Structure Study.
- Unit 3 — Algorithms and Efficiency: a race you can time, searching, sorting, and a vocabulary for the difference, ending with every team defending its algorithm choices out loud.
- Unit 4 — Building Software Together: version control, inherited code, testing what you did not write, code review, and ethics — ending at The Handover.
Running underneath Units 3 and 4 is The Software Project: a real community partner, their problem in their own words, and a team build that is version-controlled, reviewed, documented, and handed over so it outlives the people who wrote it. The Maintenance Sprint sits inside that stretch, because most of professional work is code somebody else started.