โ† Series HomeWorkshop 1Workshop 2View Slides โ†’
๐Ÿ“ฆ
Hardware check: You should have your BBC micro:bit V2, USB cable, and a working connection. Open makecode.microbit.org and confirm you can flash a program. Having trouble? Join the Help Room breakout during setup or Break #1.
Facilitator-led (25 min) You're doing (165 min) Breaks (20 min)
8:30
You Do10 min
Hardware Check + Icebreaker
Hold your micro:bit up to the camera! While TAs verify everyone's connection, open MakeCode and flash the default "Hello" program to your micro:bit. If it works, you're golden. If not, join the Help Room breakout.
โ†’ Open MakeCode
8:40
Admin5 min
Pre-Survey
Quick survey while the last hardware connections come online.
โ†’ Open Pre-Survey
8:45
ListenContextualize5 min
CRAFT Orientation + Where IoT Lives
Quick CRAFT intro (Cโ†’Rโ†’Aโ†’Fโ†’T). Then: IoT in the real world โ€” smart farms, wearable health tech, traffic systems. Every phone in your pocket is an IoT device. Today you become the engineer who programs one.
8:50
You DoContextualize8 min
Brainstorm: IoT in Your Subject
In the shared doc: Name one real-world sensor or data-collection scenario that connects to a topic you teach. (Temperature in a greenhouse = biology. Accelerometer on a roller coaster = physics. Light sensor for accessibility = CS.) Star your favorite from someone else.
โ†’ Open Shared Doc
8:58
You DoReframe3 min
Poll: When You Hear "Coding"โ€ฆ
What image comes to mind? (a) A dark screen with green text, (b) A kid in a robotics club, (c) Something I don't do, (d) Physical things happening. Vote!
9:01
ListenReframe5 min
Coding Is Physical, Not Just Screens
The reframe: computing is PHYSICAL. Sensors collect real data. Actuators change the real world. And LLMs can help you write the code โ€” the skill is knowing what to ask for and how to verify.
9:06
You DoReframe9 min
Breakout: What Stops You from Teaching with Hardware?
In small groups: What's the #1 barrier to using physical computing in your classroom? (Cost? Time? Your own comfort? Curriculum fit?) Brainstorm one way the micro:bit + LLM combo addresses that barrier. Share out to whole group.
9:15
Break10 min
Break #1
Last chance for hardware troubleshooting โ€” TAs in the Help Room breakout. Everyone else: stretch and make sure MakeCode is open and ready.
9:25
ListenAssemble10 min
I Do: First Sensor + LLM Assist
Watch: we read the temperature sensor in MakeCode and display it on the LED matrix. Then we ask an LLM: "Write MakeCode pseudocode for displaying temperature on a micro:bit" โ€” and compare its suggestion to what we built. Then we add the light sensor to the same program.
9:35
You DoAssemble15 min
Guided: Build Your First Sensor Program
Replicate what you just saw: in MakeCode, read the temperature sensor and show it on the LED display. Got it working? Add the light sensor too. Feel free to ask an LLM for help โ€” paste "How do I read the light level on a micro:bit in MakeCode?" and see what it says. Flash it to your micro:bit and test.
โ†’ Open MakeCode
9:50
You DoAssemble30 min
Breakout: Multi-Sensor Challenge
In your group, build a program that combines 2+ sensors and triggers an action. Ideas: LED alert when temperature is high AND light is low. Shake detector + compass for direction. Sound level + temperature for "classroom comfort index." Use an LLM to help write or debug your code. Document in the shared doc: what you asked the LLM, what it got right, what you fixed. Everyone programs their own micro:bit.
10:20
You DoAssemble25 min
Level Up: Choose Your Track
Track A: MakeCode+Extend your project: add data visualization on the LED matrix, radio communication between two micro:bits, or more complex sensor logic. Push MakeCode to its limits.
Track B: MicroPythonConvert your MakeCode project to Python using the micro:bit Python editor. Ask an LLM: "Convert this MakeCode to MicroPython for micro:bit." Then verify it actually works on your device.
โ†’ Open micro:bit Python Editor (Track B)
10:45
Break10 min
Break #2 โ€” Show & Tell
Post a photo or screenshot of your micro:bit doing something cool in the chat. Brag a little.
10:55
ListenFortify5 min
Demo: Does Your Sensor Tell the Truth?
Watch: we cover the light sensor โ€” does the reading drop? Breathe on the temperature sensor โ€” does it rise? Compare to a real thermometer. Something's off...
11:00
You DoFortify15 min
Experiment: Verify YOUR Sensor Data
Run these tests on your micro:bit: (1) Cover the light sensor โ€” does the value go to 0? (2) Put your thumb on the CPU โ€” watch the temp rise. (3) Compare the temp reading to any thermometer you have. Apply the Check the Machine protocol: Task โ†’ Before (what I expected) โ†’ After (what I got) โ†’ Takeaway. The micro:bit temp sensor reads CPU heat, not ambient air โ€” that's a real engineering calibration problem! Verification isn't just for AI โ€” it's for ALL data.
11:15
ListenTransfer5 min
CRAFT Debrief: What Just Happened?
Walk through today's session โ€” every activity mapped to Cโ†’Rโ†’Aโ†’Fโ†’T. Plus: how all three workshops connect: AI co-pilot (#1) + verification (#2) + physical computing (#3) = your integrated STEM toolkit.
11:20
You DoTransfer18 min
Build: Your IoT Lesson for Monday
Open the NGSS-aligned IoT lesson template. Customize it for YOUR classroom: (1) Pick your sensors. (2) Define the data collection task. (3) Write the student-facing Check the Machine prompt. (4) Note the NGSS standard it hits. Pair-share when done: "What's the first IoT lesson you're going to try?"
โ†’ Open IoT Lesson Template
11:38
You Do10 min
Explore: Your Hardware Toolkit
Browse your resources: MakeCode project files, MicroPython starters, sensor reference guide, NGSS alignment crosswalk. The micro:bit is yours โ€” take it to your classroom.
โ†’ Google Drive Folder
11:48
Admin12 min
Post-Survey & Closing
You just programmed a physical computer using AI as your co-pilot and verified the results like an engineer. Your students can do this too.
โ†’ Open Post-Survey