Skip to main content

Tackling Technical Debt- Where to start?

Every software project accumulates technical debt. Like financial debt, it compounds over time if left unaddressed, making future changes increasingly difficult and expensive. But knowing where to begin tackling technical debt can be overwhelming.  As our time is limited, we have to choose wisely.

I got inspired after watching Adam Tornhill  talk called Prioritizing Technical Debt as If Time & Money Matters. So before you continue reading this post, check out his great talk:

Back? Ok, let’s first make sure that we agree on our definition of ‘technical debt’…

Understanding Technical Debt

Technical debt isn't just "bad code." It represents trade-offs made during development—shortcuts taken to meet deadlines, features implemented without complete understanding of requirements, or design decisions that made sense at the time but no longer fit current needs.

Technical debt manifests in several ways:

  • Code smells: Duplicated code, overly complex methods, and poor naming conventions
  • Architectural issues: Components that are tightly coupled, poorly defined boundaries, or misaligned with current business needs
  • Missing practices: Inadequate test coverage, outdated documentation, or manual deployment processes
  • Outdated dependencies: Frameworks, libraries, and tools that are no longer maintained or compatible with newer systems

Where to start?

OK, time to tackle the real topic of this post; where do we need to start when tackling technical debt? In a large and complex codebase there are typical a lot of places where technical debt can be found. The way that Adam explains in his talk is by looking for ‘hotspots’ in your code, code that changes a lot:

It doesn’t make much sense to tackle technical debt in code that is never touched or changed. However if you combine this change frequency with any of the available static code analysis tools available to identify technical debt, you can easily craft a list of places where to look first.

You can identify these hotspots in a (git) codebase directly using git:

git log --format=format: --name-only --since=12.month \
| egrep -v '^$' \
| sort \
| uniq -c \
| sort -nr \
| head -50

This will return the list of most frequently modified files in the last year based on the number of commits:

While writing this post, I found that there are multiple tools out there that can help you identify these hotspots. I tried Hotspot, a .NET Global tool that combines your git change history with some complexity metrics to identify possible hotspots.

I first installed the tool using:

> dotnet tool install -g hotspot
You can invoke the tool using the following command: hotspot
Tool 'hotspot' (version '0.0.4') was successfully installed.

Now I can invoke it using:

> hotspot recommend

I tried it on an (older) project and I got the following output:

 

Nice!

More information

Prioritizing Technical Debt as If Time & Money Matters • Adam Tornhill • GOTO 2022

Understanding Technical Debt

Lehman’s Laws of Software Evolution

Hotspots — CodeScene 1 Documentation

dburriss/hotspot: A dotnet command-line tool for analysing code risks like high complexity, size, and bus factor.

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

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