My work uses MS Teams and Sharepoint, and MS is dumbing down both products as much as is feasible in order to force people to use CoPilot more. It’s moronic, and I hate discovering changes to the UI that appear to be bugs and then finding out it was deliberate. (Like buttons and scroll bars that are invisible until you hover a cursor over them. Stupid.)
But LLM’s were only ever useful if the validation of their output didn’t outweigh the supposed time saved, and that is rarely the case.
Stupid business practices. Can’t wait for a popping of the bubble.
Teams implementation of copilot was done poorly. I’ll use it sometimes by clicking copilot in the upper right corner. Its 50/50 after I use copilot in teams that a window will cover up the left side where all my chats are and it won’t go away. I have to actually right click and quit teams to get the chats with people back up.
Clearly there was minimal testing by Microsoft before they rolled out copilot in teams.
Clearly there was minimal testing by Microsoft before they rolled out copilot in teams.
Oh yeah. They rolled out an update a month or two ago that turned notifications for project tasks I had that I had flagged for higher importance, inexplicably. Absolutely infuriating stuff happening with their vibe coders.
if the validation of their output didn’t outweigh the supposed time saved
This is the key. LLMs are (somewhat, there are style and maintenance issues)) useful where things are easy to prove correct, like mathematics (there are theorem validity provers) or programming (does it compile, pass tests).
Most of the rest of the world is not like that and tasks require judgement, so people need to validate that the LLM didn’t ‘hallucinate’ (bullshit anthropomorphic word for ‘get it wrong’) again.
In subtle domains finding if an error exists can take longer than doing it yourself, with a worse failure rate, especially as skills atrophy. Same thing happened on production lines with the introduction of robots.
Yup.
My work uses MS Teams and Sharepoint, and MS is dumbing down both products as much as is feasible in order to force people to use CoPilot more. It’s moronic, and I hate discovering changes to the UI that appear to be bugs and then finding out it was deliberate. (Like buttons and scroll bars that are invisible until you hover a cursor over them. Stupid.)
But LLM’s were only ever useful if the validation of their output didn’t outweigh the supposed time saved, and that is rarely the case.
Stupid business practices. Can’t wait for a popping of the bubble.
Teams implementation of copilot was done poorly. I’ll use it sometimes by clicking copilot in the upper right corner. Its 50/50 after I use copilot in teams that a window will cover up the left side where all my chats are and it won’t go away. I have to actually right click and quit teams to get the chats with people back up.
Clearly there was minimal testing by Microsoft before they rolled out copilot in teams.
Oh yeah. They rolled out an update a month or two ago that turned notifications for project tasks I had that I had flagged for higher importance, inexplicably. Absolutely infuriating stuff happening with their vibe coders.
This is the key. LLMs are (somewhat, there are style and maintenance issues)) useful where things are easy to prove correct, like mathematics (there are theorem validity provers) or programming (does it compile, pass tests).
Most of the rest of the world is not like that and tasks require judgement, so people need to validate that the LLM didn’t ‘hallucinate’ (bullshit anthropomorphic word for ‘get it wrong’) again.
In subtle domains finding if an error exists can take longer than doing it yourself, with a worse failure rate, especially as skills atrophy. Same thing happened on production lines with the introduction of robots.