The Junior Jump
summary
Argues for concrete onboarding steps: use the interview to draft a first 30 days roadmap, assign a supervised “around‑to‑it” project with visible impact, and require written docs and transcripts so juniors can self-serve. Recommends pairing, internal admin tools, package environments, conferences and books as explicit resources, and a mentorship team pattern named Bono Edge Larry Mullen. Gives practical cadences like 30 minutes with every person and weekly mentor meetings to lower the cost of asking questions.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:20Raise a couple of hands
- 4:28Resources
- 7:13Documentation
- 8:05Planning
- 9:06Balance
- 9:50Admin Tools
- 10:45Story Telling
- 11:07Mentorship
- 12:28Mentor
- 14:22Bono
- 15:17edge
- 15:48Larry Mullen
- 17:02Recap
- 17:33Questions
related talks
17mThe Junior Jump: from Student to Team Member
23mSuccessfully Onboarding a Junior Engineer in Three Steps
24mElevating Young Developers: Best practices for seasoned developers on onboardings
10mCommon pitfalls of junior developers
30mEquipping your team to support junior developers
31mFostering a Welcoming, Supporting Productive Environment for Junior Developers...
25mProper Care and Feeding of Junior Developers
28mTechnical Onboarding, Training, and Mentoring