Future of Employment: How Susceptible Are Jobs To Computerization?
turkeydance writes: What job is hardest for a robot to do? Mental health and substance abuse social workers (found under community and social services). This job has a 0.3 percent chance of being automated. That's because it's ranked high in cleverness, negotiation, and helping others. The job most likely to be done by a robot? Telemarketers. No surprise; it's already happening. The researchers admit that these estimates are rough and likely to be wrong. But consider this a snapshot of what some smart people think the future might look like. If it says your job will likely be replaced by a machine, you've been warned.
That's a little sad.
You're talking about a profession that in many cases has either no training or dubious training. Anyone here have a family member that has an addiction problem? I have a cousin that is a heroine addict and a brother that is an alchoholic. My brother is also bipolar and god knows what my cousin is at this point... because the drugs do damage the brain.
But the point is that I've some experience with these people and they're often very nice, sometimes they're quite smart... but this is not what I'd call a "science" or even "medicine". A lot of it is witch doctorism. And that can make people feel better. But that is because the believe it works.
Here is a better list:
1. Artists: Computers are terrible at art.
2. Any kind of design or engineering work. Computers will be used as tools but they're not going to do the actual design work. They might automate the implimentation of previously designed concepts. We see that with CPU design where in something designed once is replicated by computer. But the actual design was done by humans.
3. Maintenance and repair work. Repairs are almost never carried out by a machine. You can find a factory that is 100 percent automated and it actually still has human repair techs keeping the robots working.
4. Programmers are not getting automated. The reasons are many but mostly the issue is that we've yet to come up with a machine that can self program or can accept instructions to write a program and then translate that into code with any competence.
5. Construction work on buildings is unlikely to get automated. You're seeing people do prefab and even talking about 3d printed houses etc but even if you include that there is going to be a lot of human labor happening around that.
I could go on... the fears of everyone losing their jobs to robots are ill founded. They're actually going to save us from having to do jobs we hate. Name a job a computer does that you'd actually want to do? There aren't any.
I've decided to stop wasting my time responding to AC trolls/sockpuppets... so if you want a response from me... login.
The one major complication to keep in mind is that robots/automation almost never literally 'replace' you. Rather, they allow for a different way of doing things that no longer requires you.
Robots built to replicate human capabilities are, despite continued effort, relatively pitiful. Competent bipedal locomotion, a couple of dexterous hands, fallible but very, very, adaptable image recognition, etc. are a fairly tricky package to put together on a reasonable budget. Outside of tech demos, that's why you don't bother to build the robot to resemble the worker, you restructure the task to play to the strengths of the robot(see basically all contemporary manufacturing processes). This task restructuring can also involve the user: replacing a telephone operator, say, would have been impossible until relatively recently; you need speech recognition software good enough to do the job and computers cheap enough to run it. So we didn't: Pulse code dialing allows line switching to be done with relatively simple electromechanical devices, which is why operators were on their way toward the exit more than a century ago, despite AVR 'agents' still being considered lousy and terrible to work with today.
You will almost always be misled if you try to predict odds of replacement based on 'what the job requires' rather than 'what the job produces'. Beating the people currently doing a job at the skills that the job requires is difficult, frequently impossible or uneconomic. Achieving whatever goal their job exists to fulfill(or achieving something else that eliminates that goal); is almost always how it gets done.