How I'm still not using GUIs in 2019: A guide to the terminal

Re:How I'm still not using GUIs in 2019: A guide to the term... by lm28469 on Friday March 01, 2019 @05:19AM (#19279284)

> 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.

[ Parent | on HN ]

Re:How I'm still not using GUIs in 2019: A guide to the term... by flukus on Sunday March 03, 2019 @05:59PM (#19297477)

Code 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.

[ Parent | on HN ]