@pete-s said in Does a script imply Automation?:
For instance a motor in a car runs by itself. But that doesn't make the car automated. Because the control of the car is not automated
Except that is automated compared to where it initially started. It's very automated in the sense that I don't have to get out and crank start my car or fill it with oil after every trip because it's assumed my oil will just leak out of my engine like they did when they first arrived.
You're proving my point. Automation changes over time. What we count as automated today will just be something we take for granted tomorrow. Which is why I used the example of lower level concepts. Those used to be manual things, and are now "automated" because we don't even think about them. But we don't really call that automation.
A script that echoes "hello world" is not automation but is a script.
In my mind for it to count as automation, the work the script does has to be less than equal to the amount of work it would take to do the task manually (with the caveat that the work is useful). This would incorporate tying larger initiatives together.
And we are back to what most of the discussions are on this site, it's opinion. The person talking to Gene clearly didn't think whatever the script was counted as automation. He's fully in his right to think that because a lot will agree with him.
I'm more interested to know what the script did or is going to do and we could determine whether it should be counted as automation.