Codebase Navigation Techniques
Discussions center on methods for effectively reading, navigating, and comprehending large codebases, such as code folding, printing code for overview, and IDE features, often debating their benefits over direct linear reading.
Activity Over Time
Top Contributors
Keywords
Sample Comments
It's a better navigation and overall quicker way to read code
Had the same experience, found it easier to just read the code .
I don't understand: surely with pencil and paper you are able to see the code you are editing?
How is more code on the same screen a good thing?
I could see this being helpful for potentially navigating a large codebase, especially for newer employees. could help integrate them into the team / project much faster.
Code folding is phenomenal for understanding a codebase and I'm really surprised it wasn't utilized more.
From my experience, it's just good enough to give you a code overview of a codebase you don't know and give you enough implementation suggests to work from there.
If you have a lot of code printing it all out and laying it out on a spare desk - so you can look at all the code in one go is still useful.
Does it make much difference for looking at code?
"In my IDE I'd have no trouble"But if you were reading the code on github, on a blog post, or in a chat you wouldn't have that advantage.