The thing that is missed in most efforts to replace people with machines is how often the people that are being replaced are on the fly fixing the system the machine is intended to crystallize and automate.
> how often the people that are being replaced are on the fly fixing the system the machine is intended to crystallize and automate.
If the system is broken, this is actually a good thing.
I have some experience doing automation work in small and large scale factories. When automating manufacturing work you almost always discover some flaws in the product or process that humans have been covering up as part of their job. These problems surface during the automation phase and get prioritized for fixes.
You might think you could accomplish the same thing by directly asking the people doing the work what could be improved, but in my experience they either don’t notice it any more because it’s part of their job or, in extreme cases, they like that the inefficiency exists because they think it provides extra job security.
This is exactly why “automation” hasn’t taken _that_ many jobs. It is a totally overlooked detail. Thanks for the reminder.
And then, how often they aren't[0]
[0]: "Computer Says No" https://www.youtube.com/watch?v=x0YGZPycMEU
This is what a lot of people miss about "AI will replace" programmers narrative.
When converting from a traditional process to an electronic one, half my job is twisting people's arms and playing mind reader trying to determine what they ACTUALLY do day-to-day instead of the hypothetical offical, documented, process.
Some of the workarounds that people do instead of updating the process are damn right unhinged.