alt Hacker NewsI had a WTF moment last week, i was writing SQL, and there was no autocomplete at all. Then a chunk of autocomplete code appeared, what looked like an SQL injection attack, with some "drop table" mixed in. The code would have not worked, it was syntactically rubbish, but still looked spooky, should have made a screenshot of it.
Replies
The last time I asked Gemini to assist me with some SQL I got (inside my postgres query form):
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
Same thing happened to me today in vs code. A simple helm template:
```{{ .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.
The problem with scrapping the web for teaching AI is that the web is full of 'little bobby tables' jokes.
This is the most annoying thing, and it's even happened to Jetbrains' rider too.
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.