Deep End Diving: Getting Up to Speed on New Codebases
summary
A short checklist of what actually changes onboarding: results from a 20-person survey that highlights stress management, readable patterns, and mentorship; concrete practices like an assigned buddy, semi-regular 30-minute check-ins, and pair programming; tool-level habits such as documenting decisions in PR bodies, descriptive tests, and noting exact framework versions (Rails and React syntax differences at workforce.com); and the claim that baking mentorship into schedules speeds ramp-up and reduces imposter-driven errors.
AI-written summary · about
chapters (6)
- 0:00Onboarding new devs
- 4:17Stress in onboarding
- 11:41Documentation clarity
- 17:55Teamwork strategies
- 27:50Mentorship workflows
- 28:53Q&A
related talks
24mElevating Young Developers: Best practices for seasoned developers on onboardings
39mNew Dev, Old Codebase: A Series of Mentorship Stories
37mNew dev, old codebase: A series of mentorship stories
32mHow to Be Well Onboarded as a Junior Developer Who Retrained
30mEquipping your team to support junior developers
33mTapping into the power of junior developers
38mQuit Frustrating Your New Developers - Tips From a Teacher
28mTechnical Onboarding, Training, and Mentoring
