So You Automated Your Coworkers Out of a Job (gizmodo.com)

merbs writes: Automation is too often presented as a faceless, monolithic phenomenon -- but it's a human finger that ultimately pulls the trigger. Someone has to initiate the process that automates a task or mechanizes a production line. To write or procure the program that makes a department or a job redundant. And that's not always an executive, or upper-, or even middle management -- in fact, it's very often not. Sometimes it's a junior employee, or a developer, even an intern.

In a series of interviews with coders, technicians, and engineers who've automated their colleagues out of work -- or, in one case, been put in a position where they'd have to do so and decided to quit instead -- I've attempted to produce a snapshot of life on the messy front lines of modern automation. (Some names have been changed to protect the identities of the automators.) We've heard plenty of forecasting about the many jobs slated to be erased, and we've seen the impacts on the communities that have lost livelihoods at the hands of automation, but we haven't had many close up looks at how all this unfolds in the office or the factory floor.

Comments

any job that can be automated

[pezpunk]

should be.

Evolution

[chrpai]

I've spent a career automating processes. My first such innovation came in my first year and I remember having these feelings when I realized the consequences of my proposal. I spoke to my manager and she said it was our duty to make things more efficient for our customer and that if we didn't someone else would. There is always someone paying the bill whether it's customers, shareholders, private investors or tax payers or maybe in a more abstract way the environment. We always have an obligation to use those resources wisely. In the end these people will retrain and do something else as evidenced by our current unemployment rate.

Good employees are gold

[grasshoppa]

I know we're all supposed to fear automation, but the fact of the matter is humans respond best to other humans; there will always be work for people to do.

On that note; if I have a good employee, and I write some code that deprives them of anything with which to pay them for, a few things are happening, and will happen:

1) I was grossly underutilizing the good employee to begin with
2) I will find something else for this good employee to do.

Good employees are like gold; you never throw one away, or waste them in such a manner that they'll go looking for someone to better appreciate them. I realize a lot of managers don't grasp this concept, but enough do that good employees will find one if they keep looking.

Mind you; if I automate someone out of a job, and that's all they're capable of doing, they aren't a good employee. At best, mediocre, but probably lower than that. My payroll is more important to me than their want to waste my money.