I can't imagine JetBrains keep existing in the following years. Every programmer I talked to in the past year (myself included) said their job was mostly reviewing generated code. I can imagine why people still use IDE to review code, but I can't name a reason to use something as heavy as JetBrains products just to review things written by others, AI or not.

I have been a paying user for about a decade. Ironically, when I recommended their products to vim/emacs users, they usually were like "thanks, but I know vim/emacs will always exist", and now I realize they really had a point.

▲

abhi_kr 2 hours ago | parent | next [-]

You always review large code diffs by comparing them side-by-side? You never need to drop into an IDE to follow the path a branch takes? How do you review large diffs without an IDE, do you remember what every function does in a million-loc codebase?

	▲	raincole an hour ago \| parent [-]
		> to follow the path a branch takes But vscode and vim do this just as well (in my experience). JetBrains products' advantages over the most lightweight solutions for me are: - Faster intellisense at least for C# and Java - Faster syntax errors and other linting-warnings - Refactor tools - Debugger and stack state viewer I still use Rider, but I just don't think faster intellisense/linting matters to me nowadays. Refactor tools feel like something that should come with harnesses. The debugger still helps, but to be honest LLMs are better at debugging than me if you let them dump whatever information they need. Plus, even with LLMs' help, making and managing a plugin for Rider is a much heavier process than the counterparts for vim/vscode.

▲

bni 38 minutes ago | parent | prev | next [-]

IntelliJ is excellent for doing the code review. The git and diff is top notch.

Then there is the DataGrip stuff, I use it all the time.

And the HTTP client (.http files!) is also good. It has built in scripting.

Notice here that none of these activities is writing code.

This enhances the understanding of what I am building with the agents. I’m sure the lazy dev will just skip this and will never see any of this, just let Claude completely take over.

▲

__jonas 2 hours ago | parent | prev | next [-]

Interesting that you say that, the VCS / diff UI of Jetbrains has always been my favourite by far of any git UI I have tried, I feel like they have an opportunity to capitalise on that a bit more.

	▲	stephbook 2 hours ago \| parent \| next [-]
		Not if they're going to be a VSCode skin like everyone else. ThinkRail uses the VSCode editor "Monaco."
	▲	t_mahmood an hour ago \| parent \| prev [-]
		Yeah. Sometimes I have to go down to git cli, when I mess up really bad. But otherwise, nothing beats their VCS management UI, in my experience.

▲

tomjen3 an hour ago | parent | prev [-]

For a while I agreed with you, but then I realized I want my agent to have access to the same find references, index, and rename tools, and the rest of the refactor tools that JetBrains have always provided me. And I wanted to be able to use those, even if it means I'll have to pay for Jetbrains.

Just like it was inefficient for me to manually rename variables and classes, it's token inefficient for my agent to do that.

	▲	t_mahmood an hour ago \| parent [-]
		Yeah! Refactoring, is already a solved problem, and deterministic with IDE (unless you have an untyped Python codebase), now we are reinventing the wheel, in more broken ways? Want to add an additional parameter without creating a thousands of error? Change signature, Extract a part of code to another function? Extract Method. People are taking these small, but extremely useful conveniences, without waiting, without paying for tokens, for granted.