a.1.3 thinking evaluatively
It works, but is it actually good? Learn how to judge your code against the toughest criteria, from efficiency and speed to usability and ethical impact.
So, you’ve written a program and it doesn't crash. Great job! But... is it actually any good? Evaluation is the "critical friend" stage of coding where we judge if a solution is truly "fit for purpose". It’s not just about fixing bugs (that’s debugging); it’s about asking the tough questions. Is your code fast, or does it lag like crazy? Is it easy to read, or a messy spaghetti nightmare?. We also look at the bigger picture - like whether that new social media algorithm you built is fun, or if it’s accidentally creating ethical problems like echo chambers.
🧐 Sorry, I looked and there is nothing to see.
This section outlines the progressive curriculum mapping for Thinking Evaluatively. The framework traces a carefully structured pedagogical journey - from the foundational understanding of expected outcomes and basic debugging in early years, through to the advanced application of empirical Big-O profiling and rigorous white-box testing frameworks at Key Stage 5. Crucially, it intertwines the mechanical processes of software testing with robust, real-world quality metrics, challenging students to actively audit for inclusive design and to critically evaluate the profound ethical and societal consequences - such as algorithmic bias - of the computational solutions they deploy.
Last modified: March 20th, 2026
