Walkero

software engineer, Drupal follower, Docker ninja, JS explorer, PHP believer, exotic Hardware beta tester, Amiga enthusiast, truth seeker, parent & husband... at least for now...

What I love to do when I develop is to optimise as much as possible my time by finding tools that fit my needs and automating processes. The reason is that I like to be involved in many different projects running in parallel, and most of the time these are based on completely different technologies,...

You start a brand new project and you want to use Docker, but you don't know which images you should use? How to choose which image is the best one? Is it enough just to check the stars and the downloads on Docker Hub? If not, what else do you need to check?

I know, I know. It is hard to resist some times on treating Docker images like VMs. I totally get it, but I prefer to not do that. You see, there is no sense to put everything in a custom image, every server and every product you develop, with all their necessary libraries. And I will explain myself.

I like to work and experiment on totally different projects all the time. Every month I intend to put my hands on something new and interesting, discovering exciting technologies and solutions. This means that I usually find myself working on totally different things, from Electron applications to Drupal websites to python scripts or pure C code, and the list goes on and on.

The last thing that I need is to have a development environment a complete mess. But, how can you keep everything organized and clean, and most of all, flexible to change?