10.2f — Card Jam: Showcase
Card games hit different in an arcade row: you can watch a whole match over someone's shoulder, and the READ of a card game — the little math in the eyes — is visible. Jam season one ends today; the Create PT begins in three B days (11.1a). Play like it matters, because it does: your Create PT could be this game's descendant.
The arcade row, card edition. Same contract as 10.1f: host and player in equal measure. Watch specifically for the card-game-only moments:
- The hesitation hover — the tester holds a card and reads it twice. Was it confusion or calculation? Your notes say which (confusion = design debt; calculation = design WINNING)
- The rule question — anything you have to answer out loud is tomorrow's on-screen hint text
- The rematch demand — the card game's highest compliment. Log which games got one
Star votes: best rule set, best card art (your 10.2b assets), best AI personality (10.2d — could you TELL what the AI wanted?).
Retro (same four quadrants, 10.1f format) plus ONE card-jam-only question:
- What did LISTS let your game do that single variables never could? (Name the exact moment in your game that is ONLY possible because of a list.)
- Was the starter's gift — the empty methods — a good learning design, or would building from zero have taught more? (This is an 9.10 fork-ethics question in disguise.)
The bridge to the Create PT — read this twice:
- The Create PT (full
guide) requires: a list, a procedure with a
parameter, an algorithm with sequencing + selection +
iteration, a call, input → output. Your card game has
five of the six — the score line
(selection), the shuffle loop (iteration over a list),
Deal()(a call into behavior),AI_Turn()(sequencing on top of it). The one it does NOT have is the row the rubric cares about most: a procedure with a parameter that YOU designed.AI_Turn()andDeal()take no arguments, and the starter wroteShuffle's — the PT requires student-developed code, so you cannot bank a signature you inherited. Your Build Day 1 job (11.1b) is to extract one parameterized procedure of your own. Read the requirements against your own code and mark each row honestly, out loud, today. - You may even PORT this jam's code as your PT starting point — the rules allow work you wrote in class. Fork yourself: 11.1a is three B days away, and it is not a new beginning; it is a continuation.
Reflect: your own code, read cold
Which requirement from the Create PT checklist was easiest to point at in your card jam code, and which one would you still have to explain carefully to a stranger — and why that difference?
Checkpoint — before moving on, you must be able to:
- Host + play in the showcase, collecting hover/rule/rematch data
- Name the moment in your game only a list makes possible
- Check off all six Create PT requirements against your own jam code
- Arrive at the PT launch with a candidate pitch written
Reference Docs
Need a deeper explanation? These pages cover the same concepts:
- Unit 10: Jam Season — the jam archive
- Create Performance Task — what begins next
Next unit: 11.1a — Create PT Launch: Pick Your Program
Saved on this device only — the Dashboard tracks your progress.