> As of now, I don’t see any of that being the goals even let alone the result. Instead what I see is that everyone is in a race to have as much product out as possible by the same standards that applied to products made by humans, but even lesser quality.
That is, roughly, how all automation works: You build the machine that does the humans job, barely, badly. Then you improve the machine. Producing shitty output on that journey is better than producing no output, if the domain allows for it. You learn more.
> That is, roughly, how all automation works: You build the machine that does the humans job, barely, badly. Then you improve the machine
That’s not how automation works. The first thing you build is already taking care of a cumbersome part of the human jobs, even if limited in scope. The improvement part is in reliability and maintenance. Because the core problem is already solved. All that’s left are engineering issues.
So even if the first contraception is horrible, it should be clearly visible which immediate need it intents to solve, even if the full scope of changes is not known yet. But with those, there’s no need behind them, just imagined problems.
Given GP's (accurate) point about the mediocre quality of products whose production has long since been automated, I'm curious at what point you think the output stops being shitty.
That’s not really the case though. Especially in the general case. Just look at the cotton gin. No one was designing little mechanical hands to pick through cotton.
Frequently automation happens only after someone realizes that to automate the process, the process has to be completely reinvented.
I’d say that the majority of successful automation doesn’t follow an iterative path starting from build anything that does exactly what a human does because human physiology isn’t easily replicated with rotational motion.