It's good for tricking executives that can't program into thinking they can lay off their programmers.

I turned it off in the options. It was too much energy for me to keep dismissing, parsing, or correcting.

Even with it off, the autocomplete has been made less useful from previous years.

Even worse, many other features, like highlighting and syntax parsing do not work as well with the AI turned all the way off. I finally found, with trial and error, a balance I could live with (allow it to run in background but limit what it displays to me)

The only reason I have not permanently rolled back to the best version before last year is because of language and docker changes.

But, I am ready to jump ship

a year ago or so i wrote a more detailed report at their issue tracker and the response was essentially that it will evolve and hallucinations should be gone with the next update. at that point i was evaluating the "feature" involuntarily for roughly half a year and noticed only that it behaved worse and worse.

but you can turn this resource exhaustion actually off. it's just irresponsible that this isn't the default.

My opinion, as a non-programmer, but who works in the IT field and occasionally writes code, is that it is easier to find and identify code that does not do precisely what you want it to do, than it is to write all of the code from scratch.

It saves me a lot of time and effort in, like, laying out the cases and structures and files and subsections and classes that I would have otherwise spent, which are mostly pointless wasted time, and then instead allows me ro focus on what actually needs to accomplish the output I was looking for.

To be fair, once again, I am not a competent programmer at all.

Using these tools merely allows me to accomplish things that I would not have otherwise been able to accomplish on my own without a much larger investment of time and effort.