Four things go up in a two-by-two grid — values, snippets, error messages, anything — and the question is always the same: which one doesn’t belong? There is no answer key.1 Every corner can be defended, and the defence is the point: arguing a corner out loud forces the precise vocabulary that vague pointing lets you dodge.
A grid to start with
"7" | 7 |
7.0 | [7] |
Only text. Only a whole number. Only a number with a decimal point. Only a container holding a value. Four corners, four defensible claims — and four words from Variables and Data Types worth owning by the end of the round.
How to run it
- Show the grid. One quiet minute, and everyone picks a corner.
- Hands up by corner. Every corner should have takers; if one is empty, someone argues it anyway.
- Defenders speak. The rule: name the property, not the vibe. “It is the only one that could hold more values later” beats “it looks different”.
- Close by collecting on the board the vocabulary the defences used.
One variation
Students build the grids. A good grid needs four properties that overlap three ways each, which is far harder than solving one — and building a single grid teaches more than defending ten.
Argue the corner you did not pick
Once your own corner is safe, take a different one and defend it just as hard. Being able to argue all four positions is what owning the vocabulary actually means.
Footnotes
-
The format comes from a long-running mathematics teaching routine, borrowed here because programming has exactly the same problem: students who can point at the right answer but cannot say why in words another programmer would accept. ↩