I recently read an article about Sacrificial Architecture and it got me thinking on software design and longevity. In the article it actually alludes to something I thought of when thinking of what Sacrificial Architecture would mean.
This is a short post about a phenomenon I have seen already in the past years. Every time we build a project the developer makes everything work locally in whatever way is known to him. So either using a service or own docker images or installing the actual software on the host system.
No I have not caved and suddenly love Kubernetes. Also this is probably the best topic so far that has given me so many things to write about so I hope you will allow me to milk it a little more.
I am not happy with Kubernetes. No, that is too soft but hating Kubernetes is too strong. It is one below hate. I dislike working with it and I advise others to take caution in wanting to use it.
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.
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.
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.
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.
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.
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.