Onboarding like Uber or Stripe is simpler than you think
summary
Uber shifts from thousands of repos and more than 4,000 services into a monorepo and solves multi‑gigabyte checkouts with Devpods — Kubernetes containers built from the production image, with IDE caches and artifacts preloaded so checkout time drops from hours to click‑to‑code. Stripe starts with long‑lived EC2 machines and Slack gating and evolves to Devboxes that are per‑branch and previewable so reviewers don’t need local checkouts. Open standards used include Dev Containers, GitHub Codespaces, Gitpod and self‑host Daytona.
AI-written summary · about
chapters (6)
- 0:00The problem of onboarding
- 1:34Traditional onboarding flaws
- 3:11Uber's devpod solution
- 6:35Stripe's dev box evolution
- 9:37Standardized environments
- 13:07Conclusion and key takeaways
related talks
18mHow DevPod Became Uber's Primary Development Environment
40mBeyond Productivity: Scaling Cloud Dev Environments for Faster Feedback & Sustaina...
22mOnboarding Doesn’t Have to Suck: Elevating Developer Onbo...
53mStreamline Cloud-Native App Development Using CDEs
41mThe Future of Writing Software Happens in CDEs
05mScale tooling before people onboarding
19mAccelerate developers with a CDE
21mEphemeral Development Environments