MAZE MASTERS: CODE & NAVIGATE

Workshop Overview This December, learners ages 8–17 will turn code into motion by programming Sphero robots to autonomously navigate a maze, just like self-driving systems plan routes, react to obstacles, and optimize decisions. The session blends short, high-energy tutorials with a hackathon challenge so participants design, build, test, and present their robot solutions while practicing teamwork and communication. We’ll run two tracks. Beginners (8–12) use Sphero BOLT and block coding to master motion, loops, and simple conditionals; advanced learners (13–17) unlock sensor-driven autonomy on BOLT/RVR with variables, events, and functions to optimize speed and accuracy. Everyone experiences the full arc—plan, prototype, debug, and present, supported by judging criteria that reward navigation, creativity, code quality, and teamwork.

Beginner Track Learning Outcomes
• Control movement with angles, speed, and timing; calibrate reliably before a run. Students love the “aha!” moment when a tiny change in angle makes the whole path click.
• Use loops and simple conditionals/events to repeat actions and react to bumps. This is where robots start to “think,” turning simple moves into smart behavior.
• Plan and test a route, measure outcomes, and iterate to improve accuracy. They’ll learn that every test is feedback—and engineers turn feedback into better code.
• Explain their logic and teamwork choices in a short presentation. Sharing what worked (and what didn’t) builds confidence and real communication skills.

Advanced Track Learning Outcomes
• Implement sensor-driven behaviors and event handlers (e.g., collision → recover path). Now the maze feels alive: the robot reads the world and adapts in real time.
• Structure programs with variables and functions for reusable movement logic. Cleaner, modular code lets teams build faster—and debug like pros.
• Debug and optimize for speed, path efficiency, and stable performance. Students move from “it runs” to “it runs reliably and fast,” which is the engineering leap.
• Present and defend design trade-offs using clear technical communication. Judges love hearing why a team chose one approach over another, own the narrative.