because that's Microsoft's business model
their products are just just good enough to allow them to put a checkbox in a feature table to allow it to be sold to someone who will then never have to use it
but not even a penny more will be spent than the absolute bare minimum to allow that
this explains Teams, Azure, and everything else they make you can think of
I hear tales of the before-times, when they had a QA department and took quality seriously.
... why, it's almost like in eliminating the QA function, we removed the final checks and balances on developers (read: PMs) from implementing whatever ass-backwards feature occurs to them.
Just in time for 'AI all the things!' directives to come down from on high.
And when you try to make it something useful, the response is usually "I can't do that"
I can't do that.
that's the one use case where LLM is helpful!
Some stuff that used to work well with smart autocomplete / intellisense got worse with AI based autocomplete instead, and there isn't always an easy way to switch back to the old heuristic based stuff.
You can disable it entirely and get dumb autocomplete, or get the "AI powered" rubbish, but they had a very successful heuristic / statistics based approach that worked well without suggesting outright rubbish.
In .NET we've had intellisense for 25 years that would only suggest properties that could exist, and then suddenly I found a while ago that vscode auto-completed properties that don't exist.
It's maddening! The least they could have done is put in a roslyn pass to filter out the impossible.
I'm a very forgetful person and easily distracted. This feature was incredibly valuable to me.
Gotta love the enshittification: "new and better" being more CPU cycles being burned for a worse experience.
I just have a shortcut to the Gemini webpage on my home screen if I want to use it, and for some reason I can't just place a shortcut (maybe it's my ancient launcher that's not even in the play store anymore), so I have to make a tasker task that opens the webpage when run.
I’m sure someone on the VS team got a pat on the back for increasing AI usage but it’s infuriating that they broke a feature that worked perfectly for a decade+ without AI. Luckily there was a switch buried in settings to disable the AI integration.
I found that it makes the AI experience so much better.
I even clicked the "Don't do multiline suggestions" checkbox because the above was so absurdly anti-productive, but it was ignored
This task cannot be accomplished
USING
standard SQL queries against the provided database schema. Replication slots
managed through PostgreSQL system views AND functions,
NOT through user-defined tables. Therefore,
I must return
It's feels almost haiku-like.I feel like this problem was far less prevalent a few months/weeks ago (before gemini-3?).
Using it for research/learning purposes has been pretty amazing though, while claude code is still best for coding based on my experience.
```{{ .default .Values.whatever 10 }}``` instead of the correct ```{{ default 10 .Values.whatever }}```.
Pure garbage which should be solved by now. I don't understand how it can make such a mistake.
We get rubbish suggestions from SOTA(tm) LLM models too, y’know.
The goal is AI everywhere, so this means top-down everyone will implement it and will be rewarded for doing so, so thrre are incentives for each team to do it - money, promotions, budget.
100 teams? 100 AI integrations or more. It's not 10 entry points as it should be (maybe).
This means for a year or more, a lot of AI everywhere, impossible to avoid, will make usability sink.
Now, if this was only done by Microsoft, I would not mind. The issue is that this behavior is getting widespread.
Things are becoming increasingly unusable.
Their new philosophy is "the user is too stupid to even think for themselves LOL." It's not just their rhetoric, it's every single choice they've made screaming out their new priorities of which user respect is both last and least
“I am going to give you the problem I have. I want you to help me work backwards step by step and give me the AWS cli commands to help you troubleshoot. I will give you the output of the command”.
It’s a combination of advice that ChatGPT gives me and my own rubberducking.
The one time I thought it could be useful, in diagnosing why two Azure services seemingly couldn't talk to each other, it was completely useless.
I had more success describing the problem in vague terms to a different LLM, than an AI supposedly plugged into the Azure organisation that could supposedly directly query information.