Companies often allow employees to use personal devices for work. This poses legal and practical challenges. How can these challenges be solved with CDEs?

Are your developers working "blindly" and pushing code changes to staging without testing them locally? What are the consequences of such an approach?

A lot has been written about the general benefits of using CDEs. But when do CDEs actually bring value?

In a recent article on rare illnesses, I encountered a puzzling statement: "Rare illnesses are the most common illnesses." This seeming contradiction becomes clear when we consider the context. Just as with the "works on my machine" problem in software deployment, the most common issues are often the rarest ones. This creates a long tail of unique problems.

What would a CDE for backend development look like and why is that a good idea? Find out in this article.

Devfile, Devcointainer, Dockerfile, Docker-Compose...what are the difference, similarities and how are they connected?

Are Cloud Development Environments just for senior developers or also suitable for juniors? The short anser is: CDEs are extremely valuable for both.

This is the last article of a 3 part series. In the first article, you learned about the challenges when devs who work on Kubernetes-based applications try to run all services locally. In the second one I showed you how quickly factorials grow when services aren’t shareable, why you most certainly already have a complex setup and what are the real costs of running everything locally. Now we take a look at the solutions.

In this post we outline why Dev Containers, Devfile, Nix and Devbox by Jetpack are NOT CDEs.