Remote Development Panel
summary
Panel argues remote development reduces setup friction and can save ~5 hours per developer per week by automating environments; major implementations use a container inside a hardened VM per developer for isolation (Codespaces), or thin clients and browser sessions for flexibility (Gitpod, JetBrains Fleet). Work concentrates on a common config (devcontainer.json) with a planned open spec and reference CLI, plus offline/local fallbacks, SSH/ orchestrator deployment options, and support for GPUs, emulators and embedded toolchains.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:12Remote Development
- 4:41What is it
- 6:27Online IDE
- 9:00Top 3 benefits
- 10:58Collaboration
- 15:24Adoption
- 20:38Desktop vs Browser
- 23:04VM vs Container
- 25:47Shift in strategy
- 29:00Configuration files
- 33:47Governance model
- 40:00Audience questions
related talks
28mEmbracing Remote Development for Local IDEs
01h 01mWish you were here: stories of building a remote development IDE
27mNavigating the Shift to Remote Developer Environments - A Year of Insights and Challenges
47mPanel: The Culture of Hybrid Work
45mDevelop in the cloud with Microsoft Dev Box
43mOut of Sight, Out of Mind: Survival tricks and tools for remote developers
48mThe Remote Revolution
42mSustaining Remote – First Teams.