The Art of Teaching
summary
Practical rules and evidence for teaching code: build schema by connecting new ideas to prior knowledge, create a no-judgment learning zone, and give explicit clues (spell out acronyms). Break explanations into 3–5 minute chunks and use pair and share plus quick checks so confusion resolves quickly. Cite Columbia 2012 (errors plus corrective feedback aid learning) and a 2010 Manila study showing persistent confusion (below 50% on an objective) destroys progress. Concrete examples include running an internal code school and debugging a React Native demo.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:57Level set on vocabulary
- 11:58Provide learners with clues
- 13:31Explain in byte sized pieces
- 15:10Check for understanding
- 19:54Drawback of Confusion
- 23:21sarcasm: pitfalls
related talks
34mThose Who Can Do Should Also Teach
24mWhat I've Learned about Learning from Teaching People to Code
24mTalk-driven development: Teaching ... in SWE
50mHow to use teaching as a learning tool
18mSelf-Directed Learning Material
49mReading Code
39mClean, Concise, Collaborative Code
24mPassing Down the Pain: Difficulties in Teaching Software Development