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.
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.
Without going into details, just recently I was able to get pretty decent business requirements from group manager, but it seems the only reason I was able to get somewhat decent idea of what they actually do, is because there was certain level of trust since we worked together previously so there was no need to bs one another. I openly stated what I thought is doable and he seemed to understand that I need to know actual use cases.
edit: Otoh, my boss is kinda giving up on automating another group's process, because he seems to be getting a lot of 'it depends' answers.
> 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.
> If the system is broken, this is actually a good thing.
Sometimes when you reveal extensive noncompliance with dumb requirements, the requirements get less dumb. Other times, the organisation doubles down and starts punishing the noncompliance.
My employer's official security policies say everyone should kensington lock their laptop to their desk at all times, even though the office is behind two guards and three security doors. Nobody does. But if someone made a load of noise about it, there's no guarantee they'd remove the widely ignored rule; they might instead start enforcing it.
Someone1234|8 days ago
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.
iugtmkbdfil834|8 days ago
edit: Otoh, my boss is kinda giving up on automating another group's process, because he seems to be getting a lot of 'it depends' answers.
Aurornis|8 days ago
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.
roughly|8 days ago
And the system is always broken. Reality is messy, systems are rigid, there always has to be a permissive layer somewhere in the interface.
michaelt|8 days ago
Sometimes when you reveal extensive noncompliance with dumb requirements, the requirements get less dumb. Other times, the organisation doubles down and starts punishing the noncompliance.
My employer's official security policies say everyone should kensington lock their laptop to their desk at all times, even though the office is behind two guards and three security doors. Nobody does. But if someone made a load of noise about it, there's no guarantee they'd remove the widely ignored rule; they might instead start enforcing it.
Dansvidania|8 days ago
threatofrain|8 days ago
ctoth|8 days ago
[0]: "Computer Says No" https://www.youtube.com/watch?v=x0YGZPycMEU