Lessons in Mentorship
summary
Mentorship speeds juniors toward competence by focusing on concrete tactics: listen first, then ask leading questions, give just enough clue to trigger self-discovery, manage frustration and step back when needed. Use checklists, contributing guides, small commits and CI (Travis CI) to automate feedback; teach debugging steps (what changed since last commit, reseed DB, rerun Chef). Example: a Capybara test can require 22 explicit setup steps. Never take their keyboard; keep scope limited to the teachable now.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 1:34Technical mentorship scope
- 2:36Programming as collaboration
- 3:38Mentoring boundaries
- 5:44Permission and control
- 6:08Active listening
- 8:12Debugging with questions
- 9:15Focus on problem resolution
- 9:57Simplify explanations
- 10:39Embrace uncertainty
- 11:41Hidden complexity
- 12:21Critique after understanding
- 13:04Feedback and confidence
- 14:07Safe space for mistakes
- 14:49Reduce setup friction
- 15:10Managing frustration
- 16:11Mental models with tools
- 17:34Teach problem-solving
- 18:14Good coding habits
- 18:58Documentation and commit practices for clarity
- 19:39Task estimation
- 20:22Breaking down projects
- 20:42Collaborate as equals
- 21:24Feedback and recognition
- 21:45Admit mistakes
- 22:48Mentorship across contexts
- 23:49Onboarding benefits
- 24:30Student perspective
related talks
37mNew dev, old codebase: A series of mentorship stories
09mHow !to be Mentored
48mA Series of Mentoring Stories
37mPairing with Intention: A Guide for Mentors
20mHelp Me Help You - Levelling up your juniors more effectively
31mThe Mentor Playbook
15mMentorship: Practical Advice for Success
09mFrom mentee to mentor: the art of asking questions that accelerate