Session 10: Coach notes
Goal of this session
This is an open-ended session. There is no “Basic checkpoint” with fixed learning goals: the goal is that every ninja builds something they came up with themselves and are proud of.
Success criteria per level:
- Basic ninja: has a working pygame window with at least one interactive element (moving, shooting, or collision).
- Advanced ninja: combines two or more mechanics from earlier sessions into one coherent game.
- Expert ninja: has a fully playable game with a beginning, an end and feedback (score, lives, win/lose screen).
Preparation (30 min before the session)
- Look through the earlier cheatsheets again: ninjas will ask questions about patterns from sessions 1 to 9. The session 10 cheatsheet combines everything; keep it at hand.
- Prepare inspiration material: printouts of the genre options or a slide with screenshot examples of simple games help ninjas who get stuck choosing a concept.
- Reminder: the game doesn’t have to be finished. Say this explicitly in the intro. A ninja who built a working movement mechanic has succeeded just as much as someone with a complete game.
Schedule (3 hours)
| Time | Activity |
|---|---|
| 0:00 to 0:15 | Welcome, explaining the free session, choosing a concept |
| 0:15 to 0:30 | Making a plan (3 questions on paper or in code) |
| 0:30 to 2:15 | Building: coaches walk around and help one on one |
| 2:15 to 2:45 | Finishing up + preparing the showcase |
| 2:45 to 3:00 | Showcase: everyone presents for 1 to 2 minutes |
The coach’s role today
Today you are less of an instructor and more of a sparring partner:
- Ask first: “What do you want to happen?” Understand the goal before you change code.
- Give hints, not solutions, unless a ninja is really stuck and the session is almost over.
- Encourage scope reduction: a ninja who wants to build an RPG doesn’t have enough time today. Help them define the smallest prototype that works.
- Celebrate every success: a moving square on the screen is a win. Say it out loud.
Common questions
“I don’t know what to make” Walk through the genre list on the worksheet with the ninja. Ask: “What kind of games do you like to play?” or “Which session did you enjoy most?” That gives direction.
“My idea is too big” Help the ninja reduce their idea to the core. Ask: “If you could build only one mechanic, which would it be?” Build that one first. Everything extra is a bonus.
“I’m already finished” Suggest: a start screen, sound effects, a second player, difficulty levels, saving the score (in a text file), or starting a new genre.
“My code doesn’t work but I don’t know why” Ask the ninja to put their plan into words: “What should happen when I press this key?” and compare that with what the code does. Debugging starts with understanding where expectation and reality meet.
Showcase facilitation
- Give every ninja a maximum of 2 minutes.
- Let the ninjas do the talking. No introduction from the coach needed.
- After every presentation: one round of applause, one positive observation from the coach.
- End with: “What are you going to add next week?”
Wrapping up the season
After the showcase:
- Tell ninjas they can take their code home (USB or email).
- Point out the “What now?” section on the worksheet for follow-up resources.
- Ask whether there is interest in the next season.
- Thank everyone: ninjas and coaches.