How to Teach New Programmers so That They Learn?
summary
Lists six concrete gaps juniors report and actionable fixes: have a clear plan for the first few days including seating hardware and reading material, schedule a weekly 30–60 minute Q&A so questions feel okay to ask, give deliberate practice not repetition — slightly harder tasks so skills grow, give clear relevant feedback focused on skills not person, share early-career screwups to normalize failure, and remember that modeling behaviors shapes what juniors copy.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:11Who am I
- 4:18What I should be telling you
- 4:40No idea whats about to happen
- 6:26Dont bother you
- 8:17Set aside time
- 9:09Youre not good enough
- 11:27Clear relevant feedback
- 14:50We get bored too
- 17:11We need deliberate practice
- 17:57We know what you think
- 21:03Were only as good as you are
- 25:35Conclusion
related talks
10mCommon pitfalls of junior developers
20mHelp Me Help You - Levelling up your juniors more effectively
59mFrom 0-60: Supercharging your Juniors
17mThe Junior Jump: from Student to Team Member
41mThe way we teach tech
30mEquipping your team to support junior developers
08mThe Noobs and the Programmers: On Teaching Programming
30mLessons Learned: A Developer's Perspective on Teaching & Learning