Things with code

Originally posted on LinkedIn Agile is here to stay. What started a few decades ago as some stubborn developers who thought they could do things better by breaking with the old way of working has turned in to the standard of today. When plucky startups proved that they could innovate and react to the market faster than the old companies, not just because they were smaller but because they worked smarter, people started to notice. With technology going at an ever faster rate, it is the only way to keep up. If it takes you five years to react to emerging technology, you are running more than four years behind the rest. So agile working is getting embraced and the de-facto standard is Scrum, which is a pretty good starting point for any agile team. With simple rules, core values, select but clearly defined processes and artifacts, it helps any team to get started. Although there are many more ways to work in an agile way, the simplicity of the rules, the clearly defined wa

Intro Although a lot of companies are moving towards the cloud, for many the on premise data centers are still important, either as an isolated, secure environment for data and work that should not leave the intranet, or as hybrid solutions (for example, data on premise, processing in the cloud). This doesn't prevent modern software development, it means that in most cases new software is written for containers. Data centers run a docker management layer like Kubernetes or OpenShift, enabling not just running containers but also maintaining the entire virtual infrastructure with load balancing and network provisioning capacity. For in house development, this might also mean that you will want to run your own Azure DevOps pipeline agents. For Kubernetes , this is simple, but for OpenShift there are a couple of things you need to take into account. Disclaimer I am not in any way or form an OpenShift specialist, the following observations came because I needed a build agent on an Ope