3 ms·
If it's a one time task then there is no need for a script, but if you have to do it again and again then it's very much worth it to write a script.
by dmortin 8y ago
If it's a one time task then there is no need for a script, but if you have to do it again and again then it's very much worth it to write a script.
- lloeki 8y agoScripts/automation can be worth it even for one-shot tasks for which time to create a script > time to do the task manually: a) They help in applying forethought to a process. Maybe you can even dry-run the thing. b) They help documenting what has been done, and how, which can be invaluable in a team setting. c) They train you into getting incrementally better at automating, and at sensing when to automate and when not to†. If it's painful, you're not doing enough of it. † I find that for the ones that would take ages to properly script, more often than not a combination of manual (like preparing a normalised input for the script using vim) and automated subtasks can do wonders, leveraging the best of wetware and software worlds.
- scarface74 8y agoThe only thing that I will do manually in any environment is putting sensitive data into configuration. With IAM roles, I can usually avoid that. I will create the roles manually. If you go by the old mantra of treating servers like cattle and not pets, you have to automate everything. My VMs (EC2 instances) can be destroyed, replicated, auto scaled, etc. at any time. I have to automate no matter how long it takes to figure out.