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.

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.

What forms of politics occur in coding? Well in particular I want to explain how teams can operate and be successful using different forms of government as the basis to form teams.

Our typical team will contain some software engineers, a team lead, some testers and a project manager.

There is a law called Amara's Law that states the following:

We tend to overestimate the effect of a technology in the short run and underestimate the effect in the long run.

This ties in with the so called hype cycle. That cycle has five phases starting at inflated expectations through disillusionment arriving on the plateau of productivity. The thing to learn is how to skip all these phases and arrive at the end immediately. I hope I will give you some insight on how to approach this.

I have read many a times a post starting with “I switched from Python to Go and I love it.” It baffled me until now. I have a hypothesis about why this happened and also how Google spreads. It does not spread like a disease and infect, it spreads more like religion and ideas can spread.

As I stand in a hot grimey late afternoon sun waiting for a delayed train I am suddenly wondering what it is people see when they look at me. What is it that they perceive with their frames of reference.

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.

This is a brief post on a phenomenon that is easy to detect but hard to combat and even harder to eradicate. The following happens more often than not, sadly. So you are in a discussion with a colleague on what kind of tech to use and it actually got started by the other colleague saying we should use this technology. We shall call the technology Starlit Snowflakes. I hope you learned by now the first and only relevant question to ask that needs a satisfying answer is of course:

I recently had a small discussion on why it is a bad thing when we can not automate, or script, something. The only argument this person had was if we spend two weeks on automating something that takes 5 minutes that is a bad thing. There are several reasons to automate procedures and saving time is not the main thing.

This post is in response to many claims of other posts stating that storing a UTC date is not enough in all situations. The most recent one that triggered me being this one. They all claim that you lose information about when something happened. I will refer to Unix timestamps when saying timestamps from now on.