Do it once, then never again, notice it is actually a nice automation trick for a common scenario, make a framework out of it, save everyone else's time while you now spend time closing issues and reviewing PR's :D
I'm surprised no one has brought this up, but one of the benefits of automation, besides the time/effort savings, is that, assuming you have correctly set up the automation, you can reliably guarantee that the task will be done correctly each time.
Say you have a task that's really simple, like copying build artifacts from the output directly to a shared release folder.
If you ask a human to do that 1000 times, he'll probably get it right 999 times, but, just 1 time, he might screw it up by copying the wrong files because he's distracted or not feeling well or whatever.
If you automate this process, you can guarantee that it will be right 1000 out of 1000 times. That's already a mental burden lifted because you know that copying the build artifact is going to work the first time, every time.
![image showing It usually takes longer to write the automation code too [OC]](b28e9f49-a034-559a-a483-9e42928049fe.jpg)
_Jent on July 29th, 2019 at 05:04 UTC »
And then you spend more time automating it than you would've ever spent actually doing it :(
gabrielfv on July 29th, 2019 at 05:13 UTC »
Do it once, then never again, notice it is actually a nice automation trick for a common scenario, make a framework out of it, save everyone else's time while you now spend time closing issues and reviewing PR's :D
EMCoupling on July 29th, 2019 at 06:35 UTC »
I'm surprised no one has brought this up, but one of the benefits of automation, besides the time/effort savings, is that, assuming you have correctly set up the automation, you can reliably guarantee that the task will be done correctly each time.
Say you have a task that's really simple, like copying build artifacts from the output directly to a shared release folder.
If you ask a human to do that 1000 times, he'll probably get it right 999 times, but, just 1 time, he might screw it up by copying the wrong files because he's distracted or not feeling well or whatever.
If you automate this process, you can guarantee that it will be right 1000 out of 1000 times. That's already a mental burden lifted because you know that copying the build artifact is going to work the first time, every time.
Remember, reliability and consistency has value!