Skip to main content

Junior developers

The last months I had to do a lot of coaching. It made me realize that it’s really hard to teach someone something you have done for years. You sometimes forget what it' is like to be a junior, you just can not understand why, what for you seems like “the simplest fundamentals”, is hard to grasp for someone else.

Some rules that I try to apply:

  1. Do not take over -  It can be really hard sometimes to not take control of the mouse and keyboard and show them what to do. But we all learn the most from our mistakes, so let them try some stuff, if it fails you can fix it together and they will understand why it didn’t work.
  2.  Show the path– Try to direct them to the path of the solution without revealing it. Draw things and have conversations, ask questions such as “what do we want to do now?” or “what do we want to accomplish?” or “What is the error we are getting? and what should we do to fix it?”
  3. Be ready to learn – I learned something from every person I worked with. Don’t judge too fast just because the idea comes from a junior developer.

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.

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

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...