3 ms·
I'm willing to agree that some problems aren't worth automating, especially when they have nasty or absent API surface, or when the task changes too much. On th
by yjftsjthsd-h 7y ago
I'm willing to agree that some problems aren't worth automating, especially when they have nasty or absent API surface, or when the task changes too much. On the other hand, looking only at time spent is also a very incomplete picture; I've written scripts for tasks that I was fine doing manually just because it allowed me to add free sanity checks and cut down on human error. (Story time: We had a regular process to clean up dev environment data. Coworker ran rm on prod data. We now have a script that sanity-checks the environment parameter and does the rm commands for you.) There's also value in speed beyond the pure time saved; as an extreme case, consider deploying a fix for a 0-day with ansible vs by hand to hundreds of hosts.
- satyrnein 7y agoThis a good companion to my sibling comment. Despite what I said about other departments, I do believe in automating all of our own (tech) stuff, basically for the reasons above: decreased error rate on sensitive tasks, ability to execute emergency tasks quickly, etc. But perhaps those are good targets for the type of task that should be automated generally.