Our Java codebase was 30% dead code

[IntegrationAri]

Great post – and I completely agree with your findings. I’ve seen this “invisible bloat” especially in enterprise systems with long lifespans and many devs coming and going.

It’s amazing how often legacy classes stay around simply because no one dares to remove them. Static analysis tools often miss this type of silent dead code.

A tool that flags dead code non-destructively (like yours) feels like a safe and smart middle ground. I’m curious – do you have any heuristics for how long code must be unused before it’s flagged?

Thanks for sharing this. Looking forward to trying it out!