> Their practical utility would plummet for the average person who isn't an expert in what they're asking. Having less skilled, or less attentive, people able to have problems solved for them correctly is the primary use case here. This is support 101 for unskilled requests for technical work: do what they want, not what they ask.
That's actually good for society. Maybe it sucks for you because it makes it harder to do what you want right now, but it's good to have humans very much in the loop and in control. Both to give people something valuable to do, and keep control of these machines.
They should be tools (amplify human skill), not replacements (eliminate the need for human skill).
Could you expand on that a bit? How is, for example, software being automated harmful for society?
> They should be tools (amplify human skill), not replacements (eliminate the need for human skill).
These are fundamentally incompatible. You can only amplify skill by making things easier for the skilled person, which will also make things easier for the unskilled person. This not being the case would require intentional poor design. If you can state any exceptions to this, I would be interesting. I'm having trouble thinking of any.
Their practical utility would plummet for the average person who isn't an expert in what they're asking. Having less skilled, or less attentive, people able to have problems solved for them is the primary use case here.
Most of the global memories I have to to encourage pushback and NOT do exactly what I saw. I want an intelligent assistant, not a "yes man".