Ask HN: How do you read and explore an undocumented codebase?
When working with a large third-party library which is open source or a large undocumented codebase left over by a previous developer, how do you go about understanding the codebase?
I can make the jumps around in multiple files and libraries to follow the flow.
I can easily setup debugging, set breakpoints, and watch what values poorly named variables carry.
It spots unused imports and variables in the code as well, which makes it easier to clean out cruft.
I have heard good things about Visual Studio Code as well, but IntelliJ gets my money every time.