I am dreadfully curious what use cases you're envisioning where a fast, bad/wrong answer is better for anything than a correct, slower answer.
Almost anything related to software development. Any answer I get online, whether from Wikipedia or a Github search or a Stack Overflow question or anywhere else, will require careful study and adaptation before I can use it. There will inevitably be things about any given solution that don't apply to whatever I'm doing, or that will be out-and-out wrong. But does that mean I'd be better off without doing a search at all? Of course not.
Same with AI. It can point me in the right direction and save me a lot of trouble, but it can't (yet) do my job for me.
When it gets 10x better -- and I'm sure it will -- then that last part can be expected to change. Which is awesome.
Meanwhile, Stack Overflow and Wikipedia and Github aren't going to get 10x better, ever. Not without cross-pollinating with AI.
Almost anything related to software development. Any answer I get online, whether from Wikipedia or a Github search or a Stack Overflow question or anywhere else, will require careful study and adaptation before I can use it. There will inevitably be things about any given solution that don't apply to whatever I'm doing, or that will be out-and-out wrong. But does that mean I'd be better off without doing a search at all? Of course not.
Same with AI. It can point me in the right direction and save me a lot of trouble, but it can't (yet) do my job for me.
When it gets 10x better -- and I'm sure it will -- then that last part can be expected to change. Which is awesome.
Meanwhile, Stack Overflow and Wikipedia and Github aren't going to get 10x better, ever. Not without cross-pollinating with AI.