- How much time you spend with navigating source code?
- How annoyed you are about that?
- What are your strategies to mitigate?
- Are there tools you using?
- What about polyglot navigation?
- How you onboard other people / point them to right locations - with context?
Ask HN: Navigating Source Code (especially on large projects)
1–6 of 6 posts
Re: Ask HN: Navigating Source Code (especially on large projects)
#2I use Code Mind Map - a Visual Studio / VS Code extension that allows you to add nodes linked to code and jump directly to the linked code on a click. I built it for myself. You can find it at https://codemindmap.com
Re: Ask HN: Navigating Source Code (especially on large projects)
#3Re: Ask HN: Navigating Source Code (especially on large projects)
#4[flagged]
Re: Ask HN: Navigating Source Code (especially on large projects)
#5LSP services make it trivial to jump to definitions, as well as local cross-references and filesystem views it's just not something that's a concern.
Could I scroll around 5ms faster with a different UI? Probably, but it wouldn't change my habits.
I use grep, emacs, and I don't feel like I have anything that needs mitigation.
Re: Ask HN: Navigating Source Code (especially on large projects)
#6[flagged]