5 ms·
My rule is: SSH to a machine and running manual commands for any non-toy systems is an antipattern. Every time you SSH to do something, it means you are missing
by outworlder 4y ago
My rule is: SSH to a machine and running manual commands for any non-toy systems is an antipattern. Every time you SSH to do something, it means you are missing automation and/or observability.
In small teams it's bad because it's a waste of time. In large teams it's bad because it creates communication overhead (it's also a waste of time but that can be often absorbed if things don't get too crazy). For a single person team it is bad because now they have to depend on their memory and shell history.
- emptysea 4y agoYeah it's really straightforward to setup Github/Gitlab/Circle/etc. to run your various deploy / ssh commands for you, then you don't need actually access to the box. Really nice being able to open up GitHub and manually kick off a deploy -- or have it deploy automatically.
- ithrow 4y agoFor a single person team it is bad because now they have to depend on their memory and shell history. There is this thing called shell scripts.
- outworlder 4y agoThe scripts can SSH to whatever. If someone is connecting via SSH and then running scripts, that's an issue.
- intelVISA 4y agoThis needs to be on a plaque somewhere. Reproducible doesn't just mean build systems!