Deleting Code Is a Senior Engineering Skill

Deleting code is a senior engineering skill. Most organisations have never treated it that way.

The PR that removes 3,000 lines of dead weight, flattens four abstraction layers, and makes the system legible again gets a quiet merge and no mention in the sprint demo.

The PR that introduces a clever new pattern gets the architecture diagram, the Confluence page, and the Slack celebration.

So engineers learn what gets rewarded. They add, they abstract, and they build on top of things that should have been buried two years ago.

I have seen codebases where 40% of the logic was unreachable. Dead feature flags from abandoned experiments. Deprecated APIs still wired up because nobody was sure. Utility classes with seventeen methods, three of which were actually called.

Nobody wrote that code to cause harm. But nobody had the mandate, or the nerve, to delete it either.

Refactoring discipline is not a cleanup task you schedule when things slow down. It is how you keep a system understandable. And understandability is what separates a team that ships confidently from one that ships with fingers crossed.

The engineers who know what to remove, and when, are the ones keeping your system alive. Most org structures have no way to recognise that.