> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/conference26/session-e-workshops/code-reading-scaffolding-the-learning.md). # Code Reading: Scaffolding the Learning Questioning, differentiating and supporting learners ## The cognitive psychology of comprehending Standard Algorithms What goes on in a learner's mind the first time they meet a standard algorithm at N5? Drawing on cognitive psychology and the Block Model, this workshop looks at how understanding of code is actually built, and where it stalls. You will then use that picture to find a learner's barrier and choose the question that moves them one step on. The same code, differentiated by questioning. You will leave with one worked example, a blank grid to build your own questions into - something to try on the next lesson. {% hint style="info" icon="school" %} **Jomon Palakudy** Classroom teacher - Computing Science, Glasgow City Council {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://upskilling.stacs.scot/conference26/session-e-workshops/code-reading-scaffolding-the-learning.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.