Skip to main content

The more you know, the more you know what you don’t know

The last weeks I interviewed a lot of people that wanted to join our company, some of them just finished their studies, some had a few years of work experience and some had years of experience working in the IT industry. If I compared CV’s between these people I noticed that their are big differences on how people rate their skills. Especially young professionals seems to be very confident that they are experts in things like HTML, JavaScript, CSS just to name a few, until the moment you really start to ask some though questions about each of these topics.

It made me think about the four stages of competence:

  1. Unconscious Incompetence. You don’t know what you don’t know.
  2. Conscious Incompetence. Now you know what you don’t know.
  3. Conscious Competence. You can think your way through an exercise and perform it with some conscious effort.
  4. Unconscious Competence. You can perform the task without thinking about it. It’s automatic. It’s burned into your body and it just knows what to do.

This is not only applicable when you are learning a new skill, but also when you want to teach this skill to someone else.

A good example is driving a car, once you know how to do it, it becomes quick an unconscious competence. The problem is that when you have to teach it to someone else, you first have to move it back to your conscious memory before you can start explaining it.

Conclusion: humans are strange creatures Smile

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