Skip to main content

How to NOT keep your software engineers…

I see a lot of organisations struggle to keep good software engineers. Although they pay their engineers well they see their best people leave and they cannot figure out why?!

Here are some of the malfunctions I noticed:

  • Respect: Treat your software engineers as overgrown children that play around with “toys”. Don’t involve them in any kind of decision making but micro manage them instead.
  • Involvement: Keep your software engineers as far away from business as possible. It’s not their job to understand business problems, their job is writing code.Don’t involve them in any kind of the non-technical decision-making processess. Throw requirements over the wall to engineering and expect them to implement it.
  • Hardware and Tooling: Provide your software engineers with outdated systems with unsufficient resources(writing code cannot require a powerful machine, right?). Deny any tool that can improve productivity and makes the life of your engineers easier. 
  • Accountability: Measure your developers on the lines of code they write(more is better), the number of bugs they create(less is better) and make exactly one developer responsible for a specific piece of code(how can you blaim the right person if multiple people work on the same code base?). Even better provide financial benefits for your top code writers. In the end software engineering is all about writing code, right?
  • Silos: Create organizational silos where engineering, testing, deployment are separated as much as possible(remember the accountability rule).

Any other unhealthy behavior you noticed?

Labels:

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

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

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