The Machine Does Exactly What You Wrote: Data, Control, Functions and the Trace Table
🎯 Today's mission briefing
We are learning to design algorithms at senior depth — choosing data types deliberately, controlling flow with sequence, selection and iteration, decomposing into functions with defined inputs and outputs, and operating on arrays — and to prove an algorithm's behaviour before implementation by desk-checking it with a formal trace table.
You'll know you've got it when:
- I can select an appropriate data type for each item of data in a problem, and explain what breaks when the wrong type is chosen
- I can write an algorithm in structured English or pseudocode using sequence, selection, count-controlled iteration and condition-controlled iteration
- I can decompose an algorithm into functions with named parameters and a return value, and explain what scope means for a variable inside one
- I can write algorithms that traverse an array or list using the accumulator and search patterns, indexing correctly at both ends
- I can complete a formal trace table for a given algorithm, state its exact output, and use the table to locate a logic error rather than guessing at it
The registration form that quietly locked out an entire age group
Connects to what your guest already knows and makes them curious. Activating prior knowledge is one of the strongest predictors of new learning.
A junior footy club on the Sunshine Coast put its player registration online over the summer. The form asked for a date of birth and worked out which age group you belonged in. It ran beautifully for six weeks. Then, on a Tuesday night in February, three families rang the registrar in the same hour: their kids could not register at all. The form kept saying 'no suitable age group found'. The registrar assumed the website was down. It was not down. Somewhere in the code, one line said 'if age is greater than 12' where it needed to say 'greater than or equal to 12', and every single child who happened to be exactly twelve fell through the crack between two age groups and landed nowhere.
Nobody was careless in any way you could see. The code was neat. It had been tested — by the person who wrote it, using their own kid's birthday, and their kid was eleven. One character. Six weeks. Roughly forty families. Senior Digital Solutions exists because errors like this are not rare accidents; they are the normal behaviour of a machine that has no idea what you meant and executes only what you wrote. The entire discipline of this subject is a set of habits for catching them before anyone else does.