Comment on AI spurs employees to work harder, faster, and with fewer breaks, study finds
brsrklf@jlai.lu 15 hours agoA co-worker not long ago had AI (fucking copilot in this case) randomly trying to analyze a spreadsheet report with a list of users.
There wasn’t any specific need to do this right now, but, curious, he let it do its thing. The AI correctly identified it was a list of user accounts, and said it might be able to count them. Which would be ridiculously easy to do, since it’s just a correctly formatted spreadsheet with each row being one user.
So he says OK, count them for me. The AI apologizes, it can’t process the file because it’s too big to be passed fully as a parameter in a python script (OK, why and how are you doing that?) but says it might be able to process the list if it’s copy-pasted into a text file.
My co-worker is like, at that point, why fucking not? and does the thing. The AI still fails anyway and apologizes again.
We’re paying for that shit. Not specifically for copilot, but it was part of the package. Laughing at how it fails at simple tasks it set up for itself is slightly entertaining I guess, thanks Microsoft.
Jesus_666@lemmy.world 14 hours ago
Oh yeah, same here except with a self-hosted LLM. I had a log file with thousands of warnings and errors coming from several components. Major refactor of a codebase in the cleanup phase. I wanted to have those sorted by severity, component, and exception (if present). Nothing fancy.
So, hoping I could get a quick solution, I passed it to the LLM. It returned an error. Turns out that a 14 megabyte text file exceeds the context size. That server with several datacenter GPUs sure looks like a great investment now.
So I just threw together a script that applied a few regexes. That worked, no surprise.