encodeering

Some time ago, I investigated how to switch from a manual docker image generation to an automated process for armhf based dockers using public CI servers. Building on a dedicated target hardware is still preferable, but most Open Source CI systems run on an x86/amd64 host at the moment.

When I started to experiment with docker, I had to run a debian system in a virtual OS as I primarily use windows for my everyday development and if you look at the development setup of our team you'll find a pretty heterogenous landscape with respect to the used OS's or IDE's. So in general, sharing (infrastructure) code for external resources and services is one thing we do to strive against this kind of fragmentation. 

Everyone can set up the required system easily and repeatable.

Writing a good test is hard, but, what does good actually mean in testing? Striving for an encompassing answer is not the goal of this post, but to focus on a single topic called state management. However, why should we bother, when many state-related topics do not become apparent in specifications, because of their isolated and predominant single-threaded nature?

We like to use services that allow us to connect with many people and share our ideas and data with them. Technologies with a broad network are more appealing to use, as they enable us to speak to people that we would never have addressed otherwise. 
However, most services run on a freemium base and we pay for this by watching advertisements, tolerating the fact, that our information is analyzed to make those more 'tailored' on the one hand and also made available to algorithms that search for a pattern on the other.