Photo: free stock photography (Unsplash licence) — see imprint
Debt is a speed tax, and you can measure it
Track how long a small, comparable change took a year ago versus today. When 'add a field to the order' goes from two days to two weeks, you have a number a CFO understands, and it is far more persuasive than any code-quality metric.
Not all debt is worth repaying
The ugly module nobody has touched in three years and which never breaks is fine. Leave it. Repay debt where you are still actively working — the interest is only painful where you keep borrowing.
Refactor with the feature, not instead of it
A three-month 'cleanup project' with no visible outcome will be cancelled in month two. Attach the cleanup to the feature that touches that code anyway — it gets funded, shipped and tested by real usage.
The hiring argument closes the deal
Nobody good wants to maintain a codebase they cannot set up in an afternoon. If your best developer leaves and you cannot replace them, the debt just became an existential problem instead of an engineering one.
- Measure debt as delivery slowdown, not code smell.
- Only repay debt in code you still touch.
- Bundle refactoring into funded features.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer