Learning to code vs. learning to automate

Re:Learning to code vs. learning to automate by blotter_paper on Sunday December 08, 2019 @06:09PM (#21739095)

I can see reading it that way. I was under the impression that the comment I was replying to was using a specific case to argue a broader claim, particularly with this sentence:

> I think the flaw with the scenario you described is that your programs are “replacing” these peoples’ “jobs”, when, in reality, we’re building tools that empower them to perform their jobs more effectively.

I took this as an attempted refutation of that comments parent based on the anecdotal account given.

[ Parent | on HN ]

Re:Learning to code vs. learning to automate by gen220 on Sunday December 08, 2019 @08:49PM (#21739828)

My bad, I did word it in a universalist way there, whereas I was trying to give an anecdote to counterbalance the claim I interpreted as “automation is bad for ops people”.

I think that the secret sauce that makes our automation “good”, is that we’re growing as a company, which effectively dictates that both the supply of new ops tasks and the magnitude of existing ops tasks are growing along with us.

If we weren’t growing, we’d be taking away work with our automation (instead of clearing the way for more, different work).

[ Parent | on HN ]

Re:Learning to code vs. learning to automate by blotter_paper on Sunday December 08, 2019 @09:42PM (#21740007)

Thanks for the clarification!

[ Parent | on HN ]