> 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-a-workshops/unpacking-the-keynote.md). # Unpacking the Keynote Critical Technology Literacy in Computing Science This interactive follow-up session provides a dedicated space for educators teaching Computing Science to unpack the core messages of Terrie-Lynn Thompson’s keynote. For educators accustomed to focusing on technical execution, syntax, and systems, this workshop offers a structured forum to process a different type of lens. We will discuss how to move beyond simply teaching how technology works, exploring how the politics, ethics, and global trends highlighted in the keynote can actively shape why and how we teach Computing Science. Instead of letting these ideas remain abstract, this session invites you to collaborate with fellow teachers to ground critical technology literacy into everyday classroom practice. Together, we will examine our own pedagogical assumptions, discuss practical ways to address digital inclusion and exclusion, and explore how to help students think critically about the societal impact of the digital solutions they create. {% hint style="info" icon="school" %} **Terrie-Lynn Thompson** Senior lecturer in Digital Media and Professional Education University of Stirling {% 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-a-workshops/unpacking-the-keynote.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.