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.

Remote Development Environments (RDEs) seem to be all the rage lately. Here’s the story of how I, as CEO, started thinking about RDEs as something we could use, to the point where we decided as a company to develop an RDE product.

Github, Gitlab, Gitpod, Coder, JetBrains – everyone is talking about remote development and developing products they call Remote Development Environments (RDEs). What’s behind all of this?

It is yet another buzz word, named Technology Trend №1 of 2020 by Gartner, to capture the renewed emphasis businesses are putting on the topic of automation.

We recently posted our very first job. Having heard so many horror stories about how hard it is to find good people, we prepared for a long and difficult journey. Two months later, we decided to hire three great candidates instead of one. Here is what we learned.

As a young software start-up, there are two things we do every day: learn a lot, and a stand-up. The first one more or less happens, the second one has become a habit almost as unavoidable as breathing. Every now and again, these two things collide and we learn about stand-ups - and about how we organise our work.

Many things are difficult for a young company. I don't need to enumerate on the many problems that come with not being established in the market yet, not having many people, processes, a brand, or money. Suffice to say that there are moments where we longingly look towards well-established companies who have left those early throes of chaos and insecurity behind them and are well settled in their ways.