> 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/ideas-for-physical-computing-in-the-classroom.md). # Ideas for Physical Computing in the Classroom Practical examples and advice on what works to engage and enthuse learners ## Beyond the Gimmick: Purposeful Physical Computing Physical computing projects are a powerful way to catch students' attention, but their real value lies far beyond the initial "wow" factor. This practical workshop explores how eye-catching, larger-than-life Raspberry Pi projects can serve as deep, objective-driven learning tools across Secondary levels rather than mere classroom novelties. Through live demonstrations and video case studies, we will break down how high-impact projects map directly to key Computing Science curriculum goals—from introducing fundamental digital making to teaching hands-on system access and network concepts. #### What We Will Cover * **S1 Digital Making Essentials**: How foundational, off-the-shelf physical computing components (such as traffic light modules) establish core hardware and logic concepts for early secondary learners. * **S3 Systems & Security** ("Hacking the Grinch"): Using interactive projects—like a talking, hackable Grinch that fires rockets or dynamic Christmas lighting—to teach network access, command-line control, and safe system testing. * **Interactive & Sensor-Driven Displays:** Examining desk-bound interactive setups, such as motion-sensing piranha plants or automated access systems (granting or denying entry), to teach input/output loops, conditional logic, and sensor integration. * **Demonstrations & Video Showcase:** See the physical piranha plant prop live in action, alongside video walkthroughs of larger setups, demonstrating how to manage and deploy physical computing in your own classroom. #### Key Takeaways * Practical strategies to align "showy" physical hardware projects with explicit curriculum learning objectives. * Inspiration and technical ideas for scalable Raspberry Pi projects across S1–S3. * Realistic insights on managing physical props, hardware setups, and student engagement in a secondary school environment. {% hint style="info" icon="school" %} **Fraser McKay** Teacher of Computing Science Saint John Ogilvie High School {% 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/ideas-for-physical-computing-in-the-classroom.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.