The average Java application contains somewhere between 10 to 50% unused and dead code. The impact of unused and dead code is felt by developers sifting through clutter to make changes, and by pipeline time from unit tests that validate the unnecessary code.
Identifying some unused and dead code is trivial: IDEs can detect private unreachable code but they miss entire classes, methods, or modules that are public because that code could possibly run (but doesn’t). In this webinar we’ll discuss ways of monitoring JVMs across different environments to identify what runs or doesn’t run in each, identify what you can get rid of, and how to work better on these larger applications.
Key Takeaways:
