Skip to main content

The biggest effect on code quality

You carefully assembled a team of great developers, a top architect, UX designers, product owners, etc… You are confident that with this team you can tackle any challenge.

However after 2 years working on the project, you have lost a lot of this confidence. The list of requested features keeps growing, existing functionality needs to be reworked because the business needs have evolved, and people work longer and longer days to still reach the predicted deadline.

What started as workarounds to reach the end goal faster has evolved to just work. Workarounds are no longer the exception but became the rule.

The solution becomes less and less stable and bugs are appearing everywhere. What is going on?

Aha, we just discovered the biggest impact on code quality. It is not the skills of the team, neither the programming language or technologies they use, it is something else.

The answer is ‘avoiding crunch mode’.

Crunch mode, also known as crunch time, describes working extra hours for extended periods to finish a project or meet a deadline. During crunch time, developers often put in intense effort to ensure timely delivery.

Studies have shown that developers who work a lot of over time causing sleep deprivation are 44% less productive. A sector which is notorious for its “crunch time” is the gaming industry. A lot of games where developers were pushed to reach the deadline resulted in buggy released and bad reviews.

Crunch is a failure of project management.

Ian Schreiber, assistant professor at the Rochester Institute of technology talked about the physiological effects of crunch time. He explains that it can even go so far that your productivity goes into the negative:

Once you get past 60 hours, your cognitive function is actually worse than someone who wasn't working at all.


As a counter movement, a game studio CEO explicitly introduced a “no-crunch” policy.

So next time your project manager on an already late project asks you to "do the extra mile", take it literally. Put on your running shoes, run until your head is clear and take a good night of sleep. The impact will be much higher than crunching yourself from deadline to deadline.

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