3 ms·
> There is no situation where the average programmer would only have access to CLIs. It was fairly typical for me to have SSH-only access to the production/sta
by yeputons 5y ago
> There is no situation where the average programmer would only have access to CLIs.
It was fairly typical for me to have SSH-only access to the production/staging server and no other tools than Vim/git to alter/store its configuration.
- franga2000 5y agoIf you have SSH, you probably have SFTP, so just mount it locally and work with your local tools. If you somehow don't have SFTP, FISH works on a bare SSH connection. Many modern tools also have native support for remote filesystems (vscode, anything from JetBrains...). Not to mention you probably shouldn't be doing that directly in the first place, especially as "just" a programmer. Sysadmins need to deal with CLI stuff, but programmers generally have no reason to. Of course many of us have both of these roles, but that's beside the point. As programmers, we should not even need to see the production server and as sysadmins, we shouldn't need to know things like gdb and proper development in CLI editors. We have the tools, we just don't use them. How many issues from bad edits in remote scripts could've been prevented if we used an IDE with linting via sftp instead of barebones vim?
- yeputons 5y ago> If you have SSH, you probably have SFTP Absolutely not always. The SSH may be provided through multiple proxies by a mess of convoluted Bash scripts. Because reasons or compliance or whatnot. > Not to mention you probably shouldn't be doing that directly in the first place, especially as "just" a programmer. Yeah, if you have a dedicated sysadmin to start with, and not just a team of five-ten-fifty enthusiasts who are fully comfortable with managing servers themselves. > How many issues from bad edits in remote scripts could've been prevented if we used an IDE with linting via sftp instead of barebones vim? Yeah, that would be wonderful.
- cerved 5y agoI like Vim. I like CLI. I like JetBrains IDEs. I use whichever tool I deem appropriate for the situation. Mastering vim/git/cli has been the most productive thing I've learnt as a software engineer. It's something I would recommend. Not to freshman student but at some point