People are Coming to My Beginning Workshop, What Now?
summary
Make the title show clear level in title and avoid promising "made simple." Write every microstep with screenshots and arrows, break long pages into small clicks (the Django Girls summary scroll problem shows overwhelm), and test the entire workshop so early finishers don't become unpaid bug-finders. For 20–50 attendees with one or two helpers use pairing cuts questions by a third to a half, show and re-show live‑coding mistakes, use post‑its/note cards/notebooks for anonymous questions, and run an exit survey in last 15 minutes.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:18My Workshop Title
- 2:34Practical Analysis Made Simple
- 3:44Intermediate Level Guide
- 4:23KnowItAlls
- 6:02Macworld
- 6:33Light Coating
- 8:23Hair Programming
- 9:36Why People Ask Questions
- 11:09What If They Dont Ask
- 12:29No Prints
- 13:04Notebooks
- 13:55Example
- 16:20Test it
- 17:43Exit interview
- 19:06Recap
related talks
22mGiving the Perfect Intro to Coding Workshop...in Python!
14mDelivery Passion
50mYou Should Be Standing Here: Learning to Present Sessions
34mThose Who Can Do Should Also Teach
30mLessons Learned: A Developer's Perspective on Teaching & Learning
20mFor the next generation: JavaScript education for a better JavaScript
07mTeaching programming to someone: do’s and don’ts
01h 29mWorkshop by Lian Li about Owning the Stage