Explicit Direct Instruction in Programming Education
summary
Argues that explicit direct instruction beats pure exploration for programming, citing a worked-example result where guided groups solve problems in one-fifth the time of unguided peers and Scratch research showing high dropout and skill plateaus. Describes interventions tested with children: teaching explicit code-reading strategies, adding tiny assessments in code clubs, and a controlled study where students vocalize code aloud each lesson — the vocalization group shows measurable gains on syntax exercises. Proposes building short, focused drills and consistent syntax vocabulary to speed skill transfer.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 2:17Defining programming
- 5:59Spreadsheets as code
- 10:43Challenges in the community
- 13:48Learning from other fields
- 17:12Teaching programming to kids
- 25:58Educational research
- 34:52The role of direct instruction
- 44:15Practical teaching strategies
- 53:09Closing thoughts
related talks
52mHow to teach programming (and other things)?
01h 01mHow to teach programming and other things?
02h 05mWhy We’re Teaching Programming Wrong: A Haskell Perspective
01h 06mKeynote: What is programming anyway?
43mHow to teach programming and other things?
45mTeach by Learning; Lead by Teaching
56mLearning to Teach Programming
24mTalk-driven development: Teaching ... in SWE