3 ms·
The "bias" is actually the learning space that the programmers chose. I think a big part of the problem is how programmers developing AI routines deal with gen
by grammarnazzzi 5y ago
The "bias" is actually the learning space that the programmers chose.
I think a big part of the problem is how programmers developing AI routines deal with generating aspects of a problem space the AI doesn't understand. Which is all of it.
I use Google voice. When I receive voice calls, the Google Voice application attempts to transcribe the voice recording.
Most of the content is fine, but when the program encounters part of the message that doesn't meet it's expectations, IT JUST MAKES SOMETHING UP SOUNDS GOOD TO IT.
So if someone leaves me the voice message "Your code is 532-94AA"
Google voice transcribes it as "Your code is 532-9488"
If my wise-cracking friend ends a a message with, "Talk to you never" Google will translate this as "Talk to you later".
If someone leaves me voice directions, "Turn <garbled> at the intersection", google will randomly pick a direction: "Turn right at the intersection".
It's like having a lazy, irresponsible assistant who really doesn't give a shit about communicating messages to you accurately. As long has he sounds good, that's all he cares about. "I don't know" isn't a concept Google AI even considers.
Instead of admitting it isn't confident about a sound, it just reaches up it's ass and makes a guess. And since AI's actual understanding of content is zero, everything sounds good to it.