Some time ago a colleague offered a cake to anyone who could assist in integrating Google's calendar and resource API. So, I do like cake and thought that I should give it a try. I started playing with the mentioned APIs and as usual, Java 8 has been chosen as a starter, which quickly led to some first results, but it would make sense to put some effort into creating a mobile application. Unfortunately, I didn't know much about Android yet, except that it's based on Java 6, resembles Swing programming and defines some custom lifecycle strategies.

Creating an armhf image on a different hardware platform requires five to ten times more patience than creating the same image on a native platform. A few months ago I've started with Travis CI to build the official docker images for armhf and very few images always exceeded to maximum build time of 50 minutes, due to some costly compilation steps. 

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.