> 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/why-do-we-teach-that-in-computing.md). # Why do we teach that in Computing? Uncovering Depth in Computing Teaching: A Collaborative Learning Experiment When introducing computing topics, teaching often concentrates on getting pupils through the immediate requirements of a course or assessment. Yet experienced teachers know there is a rich layer of tacit knowledge, context, and "disciplinary thinking" sitting beneath any specification that makes a topic truly make sense. For early career and student teachers—especially those encountering certain computing areas for the first time—building this broader awareness can feel daunting. This informal, exploratory workshop is designed as a **learning experiment** and open professional dialogue. Together, we want to explore how student teachers can best be supported to explore, assimilate, and comfortably draw on deeper topic context without feeling overwhelmed. *** #### **What We’ll Do** * **A Light Case Study (Database Concepts):** We will briefly review a few foundational database concepts to anchor our thinking and spark discussion about what sits "beneath the surface" of standard teaching materials. * **Open Discussion & Idea Sharing:** We’ll discuss how teachers gradually develop the tacit background knowledge that helps learners appreciate *why* a topic matters and how it shapes problem-solving. * **Co-Designing Support:** Neither tutors nor trainees have all the final answers yet! A primary goal of this session is to gather feedback, test ideas, and learn from participants about what kind of support, framing, or resources would actually be most useful for early career teachers. *** #### **Who Should Join?** * **Student Teachers / NQT/ teachers who are not CS-specialists, and those who are!** Whether you come from a strong computer science background or are picking up new technical topics for the first time, your perspective is vital to helping us understand what support works best. {% hint style="info" icon="school" %} **STACS Tutor team** {% 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/why-do-we-teach-that-in-computing.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.