Do not use `cd`, except when absolutely necessary (like with git repos). Seriously - it gives your command history context as all your command parameters have full paths, so you can recall them and execute them (in bash with ctrl-R or up-arrow) immediately, with minimum modification. Your command history will build up into a kind of run-book for the given machine you're working on. Working without `cd`, you might expect that you're going to have to type all your parameters as full paths, and you do, but it's not nearly as onerous as you'd expect, as long as you're working in a shell with good command history recall, such as bash or fish, as you have command/parameter completion available (in bash, using the tab key) and quite often, you can just recall the previous command and edit it for the next one.
Do not use `cd`, except when absolutely necessary (like with git repos). Seriously - it gives your command history context as all your command parameters have full paths, so you can recall them and execute them (in bash with ctrl-R or up-arrow) immediately, with minimum modification. Your command history will build up into a kind of run-book for the given machine you're working on. Working without `cd`, you might expect that you're going to have to type all your parameters as full paths, and you do, but it's not nearly as onerous as you'd expect, as long as you're working in a shell with good command history recall, such as bash or fish, as you have command/parameter completion available (in bash, using the tab key) and quite often, you can just recall the previous command and edit it for the next one.