Caring for new developers
summary
Class data show a stark dropout gap: 15 men vs 4 women certificates after nine months, and hiring churn costs about £12,000 per vacancy. Advice focuses on concrete actions: let learners drive half the pairing time with an actual timer, never silently take the keyboard, offer an example change rather than fixing everything, run 30‑minute scheduled mentor check‑ins, have new devs comment line‑by‑line on exemplar code, enforce a rubber duck baseline for reviewers, and prefer blind reviews to reduce bias.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:49OTHER DEVELOPERS
- 4:45WHY IT MATTERS
- 6:38ENCOURAGE CONFIDENCE
- 10:18CONSTRUCTIVE FEEDBACK
- 18:32PROTECT THE LEARNING
- 19:58HOW WILL I KNOW IT'S RIGHT?
- 21:49TRAITS OF A GOOD MENTOR
- 23:36WE HAVE EVERYTHING TO GAIN
related talks
30mLessons Learned: A Developer's Perspective on Teaching & Learning
24mElevating Young Developers: Best practices for seasoned developers on onboardings
01h 06mTeaching New Tricks – How to enhance the skills of experienced developers
35m10 Lessons for Growing Junior Developers
30mEquipping your team to support junior developers
17mJunioring Senior Developers
39mNew Dev, Old Codebase: A Series of Mentorship Stories
22mJunior Gems: Hiring, Valuing, and Empowering the Next Wave of Ruby Developers