It's good for tricking executives that can't program into thinking they can lay off their programmers.
JetBrains
A community for discussion and news relating to JetBrains and its products! https://www.jetbrains.com/
Related Communities
- !aqua@programming.dev
- !clion@programming.dev
- !datagrip@programming.dev
- !dataspell@programming.dev
- !fleet@programming.dev
- !goland@programming.dev
- !intellij@programming.dev
- !phpstorm@programming.dev
- !pycharm@programming.dev
- !rider@programming.dev
- !rubymine@programming.dev
- !rustrover@programming.dev
- !webstorm@programming.dev
Copyright © 2000-2024 JetBrains s.r.o. JetBrains and the JetBrains logo are registered trademarks of JetBrains s.r.o.
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.
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
Even with it off, the autocomplete has been made less useful from previous years.
and that fact really destroyed my year-long appreciation of the engineering at JetBrains.
also you can no more auto-complete to symbols defined elsewhere in your project. what a joke.
I have used them for php, ruby , database and c the last decade; spent thousands of hours using their editor.
While I had several issues and reported bugs during that time, I had no breaking changes.
Then last year I simply did not update at all. I rolled back to the last version in 2023 because the bugs from the new ai were so bad, I could not even copy paste without pasting as text only. Dozens of other new issues. Many of them, I think, only happened with large code bases.
I lost confidence in them, I am still using the last version of last year, have not looked at the bs of latest version.
Their code base was fragile, they always had issues after a major upgrade. But the new AI layer probably caused issues that will not be resolved, never mind the nonsense of whatever marketing is dictating this year
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.