this post was submitted on 11 Oct 2025
572 points (98.6% liked)
Fuck AI
4614 readers
948 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype. Proud supporter of working people. And proud booer of SXSW 2024.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My workplace has finally succumbed to the whole "we need to use AI to stay competitive" bullshit, and while my boss and my team aren't happy about it, he made it clear that execs would be looking for teams to have stories about how it's helped them work faster.
So, into the slop mines I went. Microsoft Copilot is the slop generator approved by our legal and infosec teams. I figured that I'd give it something easy, just pull me info on Exchange Online, Microsoft's corporate email system in Azure. Most of this stuff I'm already familiar with, so I'm just trying to see if it saves any time looking through Microsoft's documentation websites for specific details that they don't make obvious so you have to combine info from multiple pages.
I shit you not, every single response has had an innacuracy/issue. Many of them required follow up prompts because it gave me shit for Exchange Server instead of Online, despite how I set up the equivalent of the system prompt. I'm asking some pretty technical stuff, but it should absolutely be there in the training data.
Having a way to search the internet using natural language is useful, but that's not really what these things are. Natural language parsing is an amazing tool. I would love to see it stand on its own.
But the slop generation for responses falls flat, because it's trying to be everything for everyone. It doesn't know anything, so it can't reliably discern the difference between Exchange Online and Exchange Server (two different, but interoperable, systems with critical differences in functionality).
And all of that ignores that it's all built off widespread content theft, and the obscene resource usage, and that despite just how much shit is burning to make it work, the end result just isn't impressive.
TL;DR- It's not a threat to technology related "knowledge workers" either.
Small technical point. The documentation retrieval likely uses RAG and is not actually in the training data itself.