Skip to main content

Your most important skill as an architect

As an architect, the foremost important skill is ... empathy. It is the ability to perceive and comprehend things from the perspective of others, empathize with their emotions and feelings, and envision oneself in their position.

We live in a world where things are reduced to two camps, its us vs them. Where in fact if you take the effort to bridge the distance, you’ll see that there is more that unites us than that separates us from each other. But therefore you need to be willing to take the first step and that requires courage and empathy.

The IT industry is not different from the ‘real’ world with its own dichotomy of business versus IT. And unfortunately it always seems that these 2 camps are on a collision course, especially when things are not going as planned.

As an architect, I am continually navigating between these two "camps" or as Gregor Hophe would phrase it, I’m riding the ‘architecture elevator’. Empathy is the key to success in this profession, as it enables me to better understand the requirements of clients, stakeholders, and software engineering teams.

The good news is that empathy can be developed. As humans we are naturally wired for empathy. So start training your empathy muscle, be interested in others, learn about their needs, take the time to listen and try to understand their perspective.

I like to end with the following quote from Barack Obama:

“The biggest deficit that we have in our society and in the world right now is an empathy deficit. We are in great need of people being able to stand in somebody else’s shoes and see the world through their eyes.”

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...