JSConf 2015 Gord Tanner
summary
Two new hires clone the repo at 9am and by lunchtime have the whole stack running and make pull requests; the claim is reproducible onboarding cuts days to hours. It uses a vagrant-based reproducible VM with automated provisioning and port-forward proxy so host commands execute in the VM, adds NFS and Git HTTP buffer fixes, forces clocks and ulimits, and ships a bin/start version gate plus live-reload and test shortcuts to keep environments in sync.
AI-written summary · about
chapters (20)
- 0:00Onboarding new devs
- 1:19First-day productivity
- 2:24Open vs closed source onboarding
- 4:10Pain of new codebase setup
- 6:00First impressions matter
- 7:45Documentation as the entry point for contributors
- 9:32Whiteboard architecture
- 10:34Command-line driven development and help systems
- 11:59Code comments: what vs why
- 13:44Vagrant for standardized development environments
- 16:15Hiding Vagrant complexity
- 18:47Provisioning scripts quirks
- 21:41Common development environment pitfalls
- 23:03Keeping virtualized environments up to date
- 24:29Live reload workflows
- 25:15Teaching system testing
- 26:41Iterative testing edge cases
- 27:02Learning from new devs
- 27:43Easier onboarding next time
- 28:05Promo code & closing
related talks
05mScale tooling before people onboarding
33mUnsucking Your Team's Development Environment
24mRemote development can improve your developers remote work experience
31mReady To Code: Automate Your Development Environment
41mHandling Monorepos Today
44mDeveloper joy with Scott Hanselman and friends
26mCodeSandbox Projects
22mOnboarding Doesn’t Have to Suck: Elevating Developer Onbo...