Mentoring, For me or not for me, that is the question
summary
Company case: a team grows 15 to 70+ developers and builds a six‑month graduate pipeline that onboards four graduates with paired buddy + mentor support; structured mentoring emphasizes scheduled time, listening, not “superhero” fixes, and measurable milestones — e.g. a refactor backlog where new hires aim for one spec per month and celebrate each win; pairing rules include “junior on the keys” and letting the learner drive while mentors guide and avoid taking over.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:50My journey
- 7:30Giving back
- 8:50Moving into management
- 10:07Types of mentoring
- 12:08Make the other person comfortable
- 13:50Change their style
- 15:57Take your time
- 22:45If you dont have time
- 24:25Milestones
- 26:17Celebrate Wins
- 27:50Create a Help Network
- 30:02What is in return
related talks
24mHow to be a good mentor
21mMentoring: A Newcomer's Perspective
21mMeaningful Mentorship for Developers
33mAdvancing your Career: Coaching/Mentorship Matters to both Mentors and Mentees
46mBecoming a mentor, why and how?
35mBecoming a mentor, why and how?
16mFrom a rebellious individualist reinventing the wheel...
50mEmpathic Mentoring for Developers - Why Should You Care, and How?