Comment on AI is rotting your brain and making you stupid
Nalivai@lemmy.world 4 weeks agoIt’s not that LLM can’t know truth, that’s obvious but besides the point. Its that the user can’t really determine when the lies are, not to the degree that you can be when getting info from a human.
So you really need to check everything, every claim, every word, every sound. You can’t assume good intentions, there are no intentions in real sence of the word, you can’t extrapolate or intrapolate. Every word of the data you’re getting might be a lie with the same certainty as any other word.
It requires so much effort to check properly, you either skip some or spend more time that you would without the layer of lies.
Jakeroxs@sh.itjust.works 4 weeks ago
I don’t see how that’s different honestly
Nalivai@lemmy.world 3 weeks ago
See, this is the problem I’m talking about. You think you can gauge if the code works or not, but even for small pieces (and in some cases, especially for small pieces) there is a world of very bad, very dangerous shit that lies between “works” and “not works”.
And it is as dangerous when you trust it to explain something for you. It’s by definition something you don’t know therefore can’t check.
Jakeroxs@sh.itjust.works 3 weeks ago
I mean I literally can test it immediately lol, a nodered js function isn’t going to be dangerous lol
Nalivai@lemmy.world 3 weeks ago
Oh yeah, you absolutely can test it.
And then it gives you (and this is a real example, with real function names removed)
find_something > dirpath
… rm - rf $dirpath/*
do_something_in_the_dir(dirpath)
And it will work, but on a failure of a first question, instead of failing gracefully it wipes your hard drive clean.
You can find shit like that on the regula Internet, but the difference is, it will be downvoted and some nerd will leave a snarky comment explaining why it’s stupid. When llm gives you that, you don’t have ways to distinguish a working code from a slow boiling trap