This course is designed to run as a community teaching system, not a one-off slide deck.
The instructor layer turns the repo into something teachable at scale. The job is not only to explain content, but to reduce dropout, make progress visible, and help learners leave every week with a proof artifact.
Delivery principles
- Make it visual first, practical second, explainable third.
- End every session with a visible proof artifact.
- Treat errors as normal. Debugging is part of the skill, not a sign of failure.
- Keep the first three weeks gentle so beginners stay in the game.
90-minute session structure
Warmup (5 min)
Recap and one small question.
Concept (15 min)
One core idea, one diagram, one analogy.
Demo (15 min)
Show the idea in reality.
Lab (40 min)
Learners do the work while the instructor circulates.
Share (10 min)
Learners show outputs.
Next step (5 min)
Make the next action unambiguous.
Dropout prevention
Week 1-2 risk
Learners think they are not smart enough.
Week 8-10 risk
Environment setup issues create invisible frustration.
Week 14-16 risk
Logic and loops start to feel abstract.
Buddy system
Known-good setup
Tiny repeatable labs
Community teaching loop
- Start of week: post focus of the week plus checklist.
- Mid-week: blockers thread.
- End of week: proof day showcase.