Unused code is a liability

When working on a complex project, such as a repository containing multiple packages, there is one insidious thing that can slow you down: unused code, scripts, and dependencies.

These can linger for a while, creating cognitive overhead as you browse through long lists of files or dependencies. Even worse, they can prevent updates due to backwards compatibility.

This tends to happen when ownership is diffused and initiatives are churned and changed. The way to regain control is to take the time to delete them bit by bit as you encounter them.

This may sound like simple advice, but in an environment with a large number of contributors over multiple years, things tend to pile up and linger.

So, take the lead by cleaning up, or better yet, create a culture of continuously removing unused code scripts and dependencies.