How to teach programming (and other things)?
summary
Research shows explicit instruction outperforms pure exploration: weekly read code aloud exercises improve students’ syntax retention, and short end‑of‑session quizzes boost memory. A survey of 100 code clubs finds 71% let kids work independently and only 23% use any assessment. A 1992 study finds studying expert code with explanations matches the learning of students who both wrote and read code. The explanation plus chunking arguments tie to cognitive load and recommend deliberate practice and worked examples.
AI-written summary · about
chapters (15)
- 0:00Introduction to teaching programming
- 1:32Spreadsheets as programming language
- 6:12Personal journey and PhD struggles
- 8:45Inclusive communities like running and knitting
- 11:15Teaching kids programming first attempt
- 13:00How most programmers self-taught
- 18:48Teaching philosophy differences
- 25:32Historical influence on programming education
- 29:07Why explaining works better than exploration
- 35:35Direct instruction in programming education
- 36:40Reading code aloud improves syntax learning
- 41:15Teaching problem-solving strategies
- 44:04Assessment in code clubs
- 46:33Learning isn’t always fun
- 48:16Summary and call to action
related talks
56mExplicit Direct Instruction in Programming Education
01h 01mHow to teach programming and other things?
49mReading Code
43mHow to teach programming and other things?
01h 06mKeynote: What is programming anyway?
01h 08mBeginner's Mind, Expert's Mind
56mLearning to Teach Programming
30mLessons Learned: A Developer's Perspective on Teaching & Learning