Laptop development is dead: why remote development is the future
<p>I have spent a decade in charge of development tooling teams. During that time, I watched the rise and fall of <a href="https://www.vagrantup.com/" rel="noopener ugc nofollow" target="_blank">Vagrant</a> and the introduction of <a href="https://www.docker.com/" rel="noopener ugc nofollow" target="_blank">Docker</a> and a plethora of other build tools. I remember when most developers had two desktops under their desks, and I helped with the mass migration to Mac laptops. I also helped develop internal platforms for self-service compute on AWS. All of these tools were intended to bring production environments closer to development and provide easy configuration and scalability of the local environment. However, none of them nailed it.</p>
<p>Since Palantir, I’ve talked to many different developer experience leads. It turns out that there are some common themes.</p>
<p><a href="https://medium.com/@elliotgraebert/laptop-development-is-dead-why-remote-development-is-the-future-f92ce103fd13"><strong>Read More</strong></a></p>