Skip to content

Teaching Model

This course is meant to be reusable by teachers who may not want the whole six-week internship. Each module should be readable as a standalone activity while still pointing back to the full robotics arc.

Module Anatomy

Each module should include:

  • Overview.
  • Learning objectives.
  • Duration.
  • Prerequisite knowledge.
  • Materials and parts.
  • Unplugged activity.
  • Plugged programming activity.
  • Extension.
  • Reflection prompts.
  • Repository links.

What To Keep Consistent

Students should repeatedly identify:

  • State: What information must the program remember?
  • Actions: What can the player, computer, camera, or robot do?
  • Rules: What makes an action legal?
  • Feedback: What changes after an action?
  • Stopping condition: How does the game or task end?

Student vs Teacher Material

Student-facing pages should focus on what students need to do and understand. Teacher-facing pages should add pacing, common misconceptions, setup notes, safety notes, and extension choices.

Modularity Guidance

When using only part of the course, keep at least one continuity link:

  • A Python-only version should still discuss how game state later becomes robot state.
  • A robot-only version should briefly revisit how Tic-Tac-Toe state and legal moves work.
  • A graphics-only version should connect drawing and event loops to camera and UI programs.