3 ms·
> Navigation is rarely the limiting factor in development speed Here in spaghetti enterprise land it is. Quite often the biggest challenge to any given story i
by flukus 8y ago
> Navigation is rarely the limiting factor in development speed
Here in spaghetti enterprise land it is. Quite often the biggest challenge to any given story is understanding the impact of a single line change on a code base.
And since we decided to split a single bowl of that spaghetti into nuget packages the more "primitive" tools like ctags are the best way to navigate the project, they don't care about pesky things like dll boundaries.
- lm28469 8y ago> Quite often the biggest challenge to any given story is understanding the impact of a single line change on a code base. Isn't that a test coverage issue more than a navigation issue ? Opening 3 files via keyboard shortcuts vs opening them by clicking on 3 different buttons won't solve spaghetti code and low test coverage.
- flukus 8y agoCode coverage is really high, legend has it that code coverage was tied to bonus a decade ago. The tests typically add more mental overhead than reduce it due to this. > Opening 3 files via keyboard shortcuts vs opening them by clicking on 3 different buttons won't solve spaghetti code and low test coverage. It doesn't solve it, but it makes it quicker and easier to navigate, it's not just the shortcuts but the navigation stack (go to declaration, go to declaration, go to declaration, pop, pop, got to declaration, pop, pop, etc) that make it easy. Tmux and/or vim are also much better at multi-window editing than IDE's which is also handy.