One day before the test. Put Unit 2’s ideas back on the big map, drill the vocabulary cold, and race through mixed traces. Retrieval, not re-reading — that’s what moves a grade.
No new reading. Everything here is from 2.1–2.18. If a term below feels fuzzy, that’s tonight’s study target.
The whole unit lived in one node: Programs. Unit 1 was
wide — a dozen ways the world becomes bits. Unit 2 was deep — one
idea, “telling the machine what to do,” taken all the way from a first
print to compound conditionals.
Re-reading the lessons feels productive and mostly isn’t. Making yourself produce the answer before checking — that’s retrieval, and it’s what actually sticks. Everything below is built to make you retrieve.
Every term in Unit 2 belongs to one of four clusters. Cover the right column and see if you can define each term before you peek.
| Region | Terms |
|---|---|
| Values & math (Wk 1) | variable, assignment, value, expression, evaluate, MOD |
| Talking to the user (Wk 2) | input, output, type conversion, string, string method, f-string |
| Making decisions (Wk 3) | Boolean value, Boolean expression, comparison operator, selection, condition, branch, elif chain, nested conditional, logical operator, compound condition, truth table |
| Process & craft (Wks 2–4) | syntax vs run-time vs logic error, purpose statement, edge case, input validation, test case |
= vs ==), and the Python/Pseudocode switch (Python
and/or/% ↔ pseudocode
AND/OR/MOD, and pseudocode’s single =
for comparison).
The eight terms most likely to appear on the test, in one line each. Read the term, say the definition out loud, then check.
% in Python. n % 2 == 0 tests even.and, or, or not.Eight mixed questions — mostly Unit 2, with a couple of Unit 0–1 System Check items mixed in, exactly like the real test. Go fast but trace on paper. Pick an answer for instant feedback.