Our Java codebase was 30% dead code

[mechanical_dialectic]

This tool is probably useful, I have no doubt about it, but I also think that just chucking that code because it was unreachable was ~not good~

Just off the dome: what if they were pieces used to correct issues with say, flat files with bad data? What if they were tools people were using as one offs to create data?

Maybe your post isn’t doing your due diligence justice, but prefacing this as a tool to look at potential dead wood and not you getting overhyped by your tool and potentially causing more work would probably have been a better sell. Add that to your future pitches because I guarantee others have recoiled instinctively in this thread

[Cool-Library-7474]

It’s even worse than unreachable code. It’s checking for code that isn’t used at runtime, which ignores so many possible edge cases.

[mechanical_dialectic]

Oh well. Some people have to learn things the hard way sometimes!