Effective Onboarding: From Zero to Full Speed
summary
Claims that half of developers report a bad or nonexistent onboarding, and prescribes three concrete steps: get the basics ready (provision laptop credentials VPN Jenkins), force a rapid documentation cadence with new hires and veterans updating and reviewing playbooks, and give new engineers a safety net of small scoped guardrails so failures are low cost. Goal is measurable: by the end of week one the newcomer can run core workflows and feel comfortable continuing.
AI-written summary · about
related talks
30mTechnical Onboarding, Training, and Mentoring
52mSpeeding Developer Onboarding: Practical Lessons
28mTechnical Onboarding, Training, and Mentoring
28mTechnical Onboarding, Training, and Mentoring
21mHow to quickly get engineers up to speed
36mHow To Onboard New Hires Into Happy and Productive Employees
22mHumanising Onboarding: Helping New Team Members Find their Feet in the World...
24mElevating Young Developers: Best practices for seasoned developers on onboardings