In the second part of the article series, we look at what the actual costs are when all services run locally and how the complexity changes when multiple versions of a software have to be supported.
Most content about CDEs is focused on the benefits of CDEs and either doesn’t really explain how CDEs work, or only touches on the subject superficially. In this blog post, I want to provide a no-bullshit overview of the architecture of CDEs and common patterns on how CDE products work.
In the first part of this 3 part article series you will learn about the challenges when running a few services on the laptop of developers and others remotely.
It can be hard to introduce CDEs in engineering teams. In a recent interview with a dev lead, this is what we heard: "Our developers are set in their grumpy old ways and unlikely to want any change. It doesn’t matter how good a tool is if the people who should use it don’t want to change their behavior.
Cloud Development Environments (CDEs) are a new product category. Many new vendors appeared on the market in the last two years, and each one has a slightly different idea of what a CDE should look like. In this article, we will explain the most common architecture and features of CDEs, and what makes Cloudomation DevStack special.
Or why governance is crucial to realising the value of automation, with practical tips on setting up a good governance framework.
For a long time, I dismissed RPA as a lightweight approach to automation. This changed only recently, when I finally came down from my high horse and really listened to a passionate RPA advocate. What he said made sense, and I want to share with you what I learned.
What's the difference between Config Based and Code Based Automation?
The perspectives of managers and developers seem to diverge strongly when it comes to the acceptance of RDEs. This article is about analysing this contradiction, the different perspectives and the reasons for it.