<aside> 🌍 This page is public. Read about our take on public when possible, private when necessary.
This is Part 1 in a series that guides you through the different adoption phases towards cloud-based, remote software development for your team.
Developers automate the world: we supercharge our own workflows, automate infrastructure, CI/CD pipelines and even create tools that write code itself. Modern software pipelines are fully automated, with one exception: developer environments. They are still brittle, tied to local machines and require nerve-wracking set-up and maintenance efforts that distract us from getting creative and productive.
<aside> 💡 The single task of setting up a developer environment could be as much as 10% of total dev time. On top of the setup, developers spend around 10h per week on dev environment management and waiting for tests and builds to complete. ,
Those issues create a huge productivity loss and are distracting us from reaching flow. More complex projects with ever increasing workloads and remote work only exacerbate the situation.
Forward thinking companies such as Google, GitHub, Facebook, Uber and Shopify have recognized this problem and have internally built solutions for these issues for a few years already.
<aside> ☁️ With Gitpod we aim to bring container-based, remote development into the cloud to the rest of the world.
If you are interested why and how those forward leaning organisations have shifted towards cloud-based development there are a couple of great resources available online: