← GCSE Computer Science

Session 14

2026-09-08 · 2026-W37

What happened

Taught arithmetic operators (P08) fully before setting any task — the deliberate fix for yesterday's session, where a Code Lab brief was set before the teaching. Warm-up 3/3 unaided: input() returns a string, what int() does, and the named-constant justification in her own words. Taught real division, integer division and modulus with 17/5 as the worked example, naming the AQA pseudo-code equivalents DIV and MOD. She then predicted 20 / 8 = 2.5, 20 // 8 = 2 and 20 % 8 = 4 correctly, modulus included. Met the float trap: predicted 60 for price + price * 0.2, corrected to 60.0 once told that a float in the sum makes the result a float, and identified int() as the fix herself. Solved Code Lab \"Adding VAT\" independently, 3/3 tests, using the constant, int() on input and int() on output; code was clean and correct first paste. Identified // for hours and % for minutes unprompted; started \"Hours and minutes\" when the block timer ended.

Planned next

Finish Code Lab \"Hours and minutes\" (P08, // and %). Then selection (P03): teach if/else with a worked example and a check for understanding BEFORE setting \"Pass or fail\", then \"Grade bands\" for elif. Warm-up should include one float-vs-int prediction (e.g. what does 10 / 5 print) and one f-string question.

What this session changed

TopicNameChangeEvidence recorded
P08Not started → DevelopingTaught 8 Sep with worked examples; predicted 20/8, 20//8 and 20%8 correctly unaided, identified int() as the fix for the float result, and solved Code Lab 'Adding VAT' 3/3 tests independently using the constant and int()
P02Developing → DevelopingWarm-up 8 Sep: gave the 'why use a named constant' justification unprompted and in her own words (written once, so easier to change) — the loose end recorded on 7 Sep is closed. Applied VAT_RATE correctly in a working program