While loops opened from zero and taken to developing: worked example → predictions → production check → Code Lab 'Until you say stop' solved in 2 runs → handwritten exit ticket 3/4. Extra session (no CS block today), elapsed ~12:30–14:35 incl. a movement break of unknown length. Starter 3/3 unaided, 0 blank: running-total trace "1, 3, 6"; temp > 25 at 25 → "fine"; range[1, 6] no colon → "the brackets are wrong and it needs a colon". Worked example (ask until "stop"): line-1 say-back produced code ("for word = stop / print("finished")"), narrowed → "The user types a word."; line 2 → "if it is not equal to, stop. Go again", binary checks cat→in, stop→"no" correct; loop without update predicted "1", guided to "It would get stuck in a loop because a word is still holding cat"; produced word = input() unprompted; print after loop correct. Predictions 2/2 (3 times; "done" for a zero-run loop). Production check: password != "banana" 1/1. Code Lab p05-stop: plan line given first; solved in 2 runs/330s, run 1 missing the second input(), found unaided (practice #46). Exit ticket (bigger than 100, handwritten, 3-item checklist given): key = input () / While key < 100 : / Key = input / print("Done") — structure right, 3/4 indicative; boundary < 100, no int(), While/Key capitalised, input missing (); fix asked → "make it 101". Gate note: the exit ticket needed int() (P17, still a gap) — a planning error, not held against her. P02 third mixed-case handwritten program despite checklist → demoted.
Open with three no-notes items one per message: fill the missing update line in a while loop; write the condition for 'keep going until the number is bigger than 50'; spot-the-error on `While Age < 18` / `age = input`. Then teach turning typed text into a number (int(input())) with a worked example and say-backs, and redo Thursday's 'bigger than 100' loop by hand with it, checklist ticked aloud before writing. Then a second while-loop task on a new context by hand.
| Topic | Name | Change | Evidence recorded |
|---|---|---|---|
| P05 | Not started → Developing | 24 Sep: taught from zero (worked example line by line with say-backs), predictions 2/2, production check 1/1 (password != "banana"), Code Lab 'Until you say stop' solved in 2 runs, handwritten exit ticket 3/4 (structure correct; boundary < 100 for 'bigger than 100', no int()). notstarted → developing, single level. | |
| P04 | Gap → Gap | 24 Sep starter, no notes: running-total for-loop trace values '1, 3, 6' correct; spotted both errors in `for i in range[1, 6]` (square brackets, missing colon) unaided. | |
| P03 | Developing → Developing | 24 Sep starter: temp > 25 with temp = 25 → 'fine' correct unaided (prediction). In production (exit ticket, while condition) wrote < 100 for 'bigger than 100'; fixed to < 101 when asked. | |
| P17 | Gap → Gap | 24 Sep exit ticket (handwritten while loop comparing input with 100): no int() on either input, so the comparison would fail at runtime. Task needed P17 while it is still a gap — set too early by the tutor; not evidence against the topic. She did write money = int(input()) unprompted on 22 Sep. | |
| P02 | Secure → Developing | Third handwritten program with mixed case (18 Sep Cost/cost; 22 Sep Cost/Print; 24 Sep While and Key capitalised) — this time despite a 3-item checklist (lowercase, round brackets, colon) given immediately before. Loose end said a third demotes. secure → developing. |