Teach This Workshop

Materials for Instructors

The Instructor Kit

As of 2026-10-09: not yet ready to teach. 0 of 15 labs have run end to end, with their current code, on the Colab runtime they are designed for. 15 have run end to end on their real path elsewhere, on another machine or on the CI runner, and 0 more in part. On the GitHub CPU runner (newest run of each notebook, 2026-10-06), 16 of 16 notebooks passed; 9 of the passing runs used test doubles, which check that the code runs, not what the models do. 8 of 11 pieces of blocking work are open. What has run, where, and what is missing.

  • Intro slides: the deck for the opening slot of Day 1, the welcome and the setup check. Days, modules, datasets and times come from _variables.yml through the generated includes, so it follows the schedule. Press ? in the deck for its keyboard shortcuts.
  • Facilitator guide: day by day, what to set up, what to say first, where groups get stuck, what to say in each debrief, what to cut when the clock slips and what to do when Colab, an API or the Hub fails. It opens with what has not yet been verified; read that first, with the readiness page, which lists what has run, where, and the blocking work that remains.
  • Pace sheet: a minute-by-minute plan for every day: each briefing’s live plan, each lab with the checkpoint participants should have passed by each point, the debriefs, and the warm-up and wrap-up of Days 2 to 5.
  • Knowledge checks: an entry check on the prerequisites and a knowledge check with one or two questions per module objective, with answers, plus one transfer question per module that changes the example.
  • Glossary and results worksheet: a term-and-symbol index for participants, and a table of each lab’s headline number beside the conditions a fair comparison needs. The day wrap-ups fill the worksheet’s tables.

The Shape of a Module

On Day 1, each module is 95 minutes: 45 minutes of briefing, then 50 of lab. On Days 2 to 5, each module is 120 minutes: 55 minutes of briefing, 55 of lab, then a 10-minute debrief. On Days 2 to 4 the second module breaks for lunch between its briefing and its lab. On Day 5, the capstone build runs on across lunch. The capstone (Module 15) has no briefing: it takes 11:30–12:25, 13:25–14:30 and 14:45–16:45 on Day 5.

Every lab follows Predict → Run → Explain → Check:

  1. Ask participants to predict the output before they run a cell.
  2. Run it.
  3. Ask someone to explain the result, especially a surprising one.
  4. Use the checkpoint cell to confirm.

Each lab has a core path planned for the lab slot and one optional stretch section. The plans are estimates until the lab has been timed on your runtime; the readiness page shows which have. If a group runs slow, skip the stretch; nothing later depends on it.

Module 0 is the exception: optional pre-work, with no briefing and no notebook. Participants work through its page on their own laptops before Day 1. On Day 1 you open the room from 08:00 to 09:00 for an optional drop-in clinic and help with installs. See its section in the facilitator guide.

Warm-Up and Wrap-Up

Days 2 to 5 open with 15 minutes of warm-up (09:00–09:15) and close with 15 minutes of wrap-up (16:45–17:00); each day page has both (Day 2, Day 3, Day 4, Day 5). Warm-up uses five knowledge check questions from knowledge checks, about three from the previous day and two from earlier days: participants answer alone on paper for 6 minutes with notes closed, compare with a neighbor for 4, and you take the two most-missed for 5. Nothing is collected or graded. Wrap-up asks what each of the day’s modules fixed and what it left open, and fills a running table of the day’s lab results with the room’s own numbers; write it on the board and keep it, because Day 5’s wrap-up, which closes the workshop, completes the same line of ideas in the capstone wrap-up.

Before the Workshop

  • Send participants the Before Day 1 page a week ahead: the entry check, the reading for any area where they miss two or more of its three questions, and setup, in that order.
  • Ask participants to complete Setup the day before, to try Module 0 as pre-work if they want it, and tell them whether the room opens at 08:00 on Day 1 for the drop-in clinic.
  • Decide whether you will provide API keys or rely on the open-model path. Both work.
  • Run every notebook on a fresh Colab runtime the week before. Colab’s preinstalled packages change. Record each run (see runs/) so the readiness page reflects it.
  • Before the first delivery, pilot the core paths with a few participants and record where they stall, following the pilot protocol. A notebook that runs is not yet a lab that fits its slot: the pilot measures participants’ time, which runs/ does not.

Reuse

The text is licensed CC BY 4.0 and the code MIT, so you may teach, adapt and share this material with attribution. The source is on GitHub.