You manage the dependencies or the dependencies will manage you.

So I had a recent discussion on what dependency management is. It turns out there are a lot of dependencies, or in other words you are dependent on a lot of different things. First we defined what a dependency is. If you like it to a machine then any moving part big or small is a dependency. From the operating system to the version of a library to version of tools being used. As you see that is quite the number of moving parts.

So why am I a big pro on using Docker or in larger projects/companies even Kubernetes? Well the biggest advantage I see and experience is that you take away dependencies from developers and non developers alike. Can you run Docker, if yes you can run the apps and the database and the frontend. What is left to be done by you? Write the code. That is it.

What now?! Another abbreviation in this gotta type fast with fewest characters possible but still convey the most information possible? Well for us developers the chance is high that you had to search something with those four chars and an Operating System as the search term.

To start off this adventure I reiterate that making your applications run in docker everywhere is a good thing. So the process of getting applications in docker is called dockerisation or to dockerise your apps. Or for you other English speakers dockerization and to dockerize. The reason for this is that in principle if you can run docker you can run the application. Now this is where Windows comes in.

In our lives we generally suck at communication or in active sense communicating our hopes, dreams, wishes, and desires to other human beings. This is because it is difficult to get communication right. Not to mention how to do it right with software.

So once in a while you feel like decluttering your life or maybe just in technical areas remove unneeded apps and libraries and clean up projects of unwanted cruft. When talking about the cloud I generally have the most experience with AWS.

So in line with previous post, there is something to be said about thinking about the environment when developing any piece of software. Most of the time we all take for granted the nearly limitless amount of resources to our disposal. Memory, CPU cycles and so on. The thing is that all costs energy to use. Energy has to come from somewhere and in general is not good for the environment, not to mention the heat you produce.

You might think what will this post be about? Well it is inspired by a tool I used called terraform . What happened was we configured it a specific way and then it still did not work in one environment but it did in another environment. Same config file but different environments? It must be doing something else under the hood. What did we do to help? Crank up the log level to the max of course.

This post is about something that is trending and me and a close friend of mine who were discussing this were both baffled by this trend. We simply don't get it. There was once the web in all it's glory in the 90s. It was only HTML. That was it. There was a markup language that showed you what needed to be put where. Then there was some styling but not a lot really.

Just a quick post that used to be about something only applicable to Java ecosystem. Nowadays it seems to be prevalent everywhere. What it is I am referring to, well we dubbed it “Downloading the internet”. It is all the dependencies and libraries and the dependencies and libraries of those dependencies and libraries ad nauseum when you are making an application that every developer seems to put in there.