> ses several classes and subclasses, with code paths that move around a lot through the class hierarchy The flip side I see more often than not (no idea if it

> ses several classes and subclasses, with code paths that move around a lot through the class hierarchy The flip side I see more often than not (no idea if it applies here) is that IDE's are the enabler that allow such terrible code where less tooling would force a much simpler and more readable design. The more tooling you need to navigate a codebase the less readable it is. The reason "you need an IDE for java" is so prevalent isn't so much because of the language but because of the "enterprisy" OO code the ecosystem is famous for. IDE's can certainly help, especially once projects reach a certain size, but reliance on them is an indicator of greater problems.