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?

Popular posts from this blog

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

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.

.NET 9 - Goodbye sln!

Although the csproj file evolved and simplified a lot over time, the Visual Studio solution file (.sln) remained an ugly file format full of magic GUIDs. With the latest .NET 9 SDK(9.0.200), we finally got an alternative; a new XML-based solution file(.slnx) got introduced in preview. So say goodbye to this ugly sln file: And meet his better looking slnx brother instead: To use this feature we first have to enable it: Go to Tools -> Options -> Environment -> Preview Features Check the checkbox next to Use Solution File Persistence Model Now we can migrate an existing sln file to slnx using the following command: dotnet sln migrate AICalculator.sln .slnx file D:\Projects\Test\AICalculator\AICalculator.slnx generated. Or create a new Visual Studio solution using the slnx format: dotnet new sln --format slnx The template "Solution File" was created successfully. The new format is not yet recognized by VSCode but it does work in Jetbr...
OSZAR »