Tapping into the power of junior developers
summary
Claims: hire juniors for diversity and fresh ideas, set them up with an onboarding buddy, give ramp‑up work like update the README, and pair constantly via a pairing channel shindigs. Survey finds ~60% say mentorship/pairing helps most, ~70% pivot into tech, ~40% struggle with impostor syndrome and ~70% consider quitting. Evidence: pairing cuts bugs ~15% (Utah) and paired work produced ~914 LOC vs ~2,200 solo (NASA). Watch for operational failures like prod credentials in onboarding docs.
AI-written summary · about
chapters (19)
- 0:00Who is speaker
- 1:00Why hire juniors
- 3:40Mentor benefits all
- 6:27Mentor junior devs
- 8:10Forbidden questions
- 9:10Fall in gaps good
- 10:30Docs always wrong
- 13:11Make great seniors
- 16:52Break barriers
- 18:01Don't isolate devs
- 19:23Good managers
- 21:11Curse of knowledge
- 22:22Be the senior
- 24:07Survey stats
- 25:14Why leave tech
- 26:11Tips for juniors
- 29:18Sometimes leave job
- 29:42You belong here
- 30:12Get in touch
related talks
30mEquipping your team to support junior developers
30mTechnical Onboarding, Training, and Mentoring
28mPair Programming as a Mechanism for Growth
34mDeep End Diving: Getting Up to Speed on New Codebases
28mProblem Solving Through Pair Programming
01h 01mPairing, Sharing, Caring - One team's journey to Pair Programming
22mJunior Engineers Are Features, Not Bugs
46mGrowing a Junior Dev into a Beautiful Coding Butterfly