Building the IDE Golden Path
summary
Cloud developer environments (CDEs) standardize the inner loop by running editors and toolchains remotely using tools like code-server, VS Code SSH, JetBrains integration and Dev Containers, and by rolling out in four stages from a universal image to team-owned clusters. Recommend keeping at most three universal images, enable Dev Containers for per-repo overrides, and use image caching and build caches to offset M1/M2 local speed. Proven at Netflix, Slack, Uber (and internal Google Sider), benefits include faster onboarding, higher time-to-first-commit, and safer tool rollouts (e.g., GitHub Copilot).
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:12Developer platform gaps
- 8:09Why now for IDE paths
- 12:45Modern dev environments
- 16:56Cloud dev environments
- 22:16Four stages of IDE paths
- 26:06Customizing environments
- 31:06Enablement and marketing
- 32:32Summary
related talks
46mSponsored Session: Building the IDE Golden Path
45mContaining Your Development – Why Cloud IDEs Are the Future
24mUnleashing Developer Productivity: Supercharging Zero Day Cloud-Native Developer...
26mScaling Enterprise Development with Cloud IDEs
48mReplace Your IDE with a CDE for Onboarding i…
18mLeveraging Standardized Dev Environments for Peak Developer Velocity
12mLocal to CDEs: Slack's Remote Development Journey
41mThe Future of Writing Software Happens in CDEs