Skip to main content

I’m a problem solver, not a coder

Last week I was reading the ‘Please don’t learn to code’ post by Jeff Atwood where he complaints about the intentions of Mike Bloomberg(New York City’s mayor) to learn coding. Although I think that Jeff is missing the point about what Mike Bloomberg is trying to achieve with this initiative, there are some other things inside his blog post that resonates with me.

Jeff talks about the fact that writing more code is most of the time not the desirable thing. It took me a long time to understand as a programmer that my job was not writing as much code as possible. Instead the real skill is writing as little code as possible.  (I think I have some colleagues that can agree that I’m more busy removing code, instead of writing Smile)

There are a lot of people out there that can code way better than me , but I do not care. I have evolved from someone who thought that coding was the goal to someone that believes that problem solving is my main job. And writing code is just a tool in my tool belt to solve these problems.

So goodbye ‘Bart the programmer’, here is ‘Bart the problem solver’.

mrwolf

Remark: If you don’t know Mr. Wolf, go watch Pulp Fiction!

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         ...