the best way to ramp up on a codebase is to simply follow the critical path and draw an execution diagram of the entire critical path. tools like these are gimmicks.
My experience with large codebases is it is hard to follow a critical path, especially with multiple things running in parallel. This leads to lots of back and forth between the new engineer and the rest of his team, taking up time for both parties -- which is why we created Codeflow.
However, if there is a better way to follow the critical path/best practices that you do follow to do so, I'd be glad to hear them!
Looking forward to any insights you may have, and thanks for the feedback
