Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Agentic Development Environment by JetBrains

air.dev

Post reply on HN
Print view View original

31–40 of 65 posts

Re: Agentic Development Environment by JetBrains

#31

Post by jasonsb »

rfw300 wrote: post #11

I'd like others' input on this: increasingly, I see Cursor, Jetbrains, etc. moving towards a model of having you manage many agents working on different tasks simultaneously. But in real, production codebases, I've found that even a single agent is faster at generating code than I am at evaluating its fitness and providing design guidance. Adding more agents working on different things would not speed anything up. Bu…

I'm with you. The industry has pivoted from building tools that help you code to selling the fantasy that you won't have to. They don't care about the reality of the review bottleneck; they care about shipping features that look like 'the future' to sell more seats.

Re: Agentic Development Environment by JetBrains

#32

Post by ivape »

rfw300 wrote: post #11

I'd like others' input on this: increasingly, I see Cursor, Jetbrains, etc. moving towards a model of having you manage many agents working on different tasks simultaneously. But in real, production codebases, I've found that even a single agent is faster at generating code than I am at evaluating its fitness and providing design guidance. Adding more agents working on different things would not speed anything up. Bu…

Right. A computer can make more code than a human can review. So, forget about the universe where you ever review code. You have to shift to almost a QA person and ignore all code and just validate the output. When it is suggested that you as a programmer will disappear, this is what they mean.

Re: Agentic Development Environment by JetBrains

#33

Post by dwb »

rileymichael wrote: post #15
ElijahLynn wrote: post #12

Earlier quoted context omitted.

Umm, it ain't ever gonna be over, it is a new era. We need to adapt to new ways of thinking and ways of working with new tooling. It is a learning curve of sorts. What we want is to solve problems, the new tooling enables us to solve problems better by letting us free up our thinking by reducing blockers and toil tasks, giving us more time to think about higher level problems. I remember this same sentiment towards A…

> What we want is to solve problems speak for yourself, i want to understand everything and be elbow deep in the code

Capital has other ideas, it wants “problems” “solved” faster and faster.

Re: Agentic Development Environment by JetBrains

#36

Post by minus7 »

minus7 wrote: post #35

JetBrains should stop building stupid AI shit and fix their IDEs. 2025 versions are bordering on unusable.

Issues I observed, mostly using GoLand:

- syntax errors displaying persistently even after being fixed (frequently; until restarted; not seen very recently)

- files/file tree not detecting changes to files on disk (frequent; until restarted; not seen very recently)

- cursor teleporting to specific place on the screen when ctrl is pressed (occasionally; until restarted)

- and most recently: it not accepting any mouse/keyboard input (occasionally; until killed))

Re: Agentic Development Environment by JetBrains

#37

Post by grim_io »

NitpickLawyer wrote: post #9
GiorgioG wrote: post #6

Can't wait for this AI shit to be over so they can get back to their bread & butter...great dev tools.

> their bread & butter...great dev tools. A cursor style "tab" model, but trained on jetbrains IDEs with full access to their internals, refactoring tools and so on would be interesting to see.

They have that now. Not as great as cursor tab, but nothing is.

Re: Agentic Development Environment by JetBrains

#40

Post by torben-friis »

rfw300 wrote: post #11

I'd like others' input on this: increasingly, I see Cursor, Jetbrains, etc. moving towards a model of having you manage many agents working on different tasks simultaneously. But in real, production codebases, I've found that even a single agent is faster at generating code than I am at evaluating its fitness and providing design guidance. Adding more agents working on different things would not speed anything up. Bu…

I really would like an answer to this.

My CTO is currently working on the ability to run several dockerised versions of the codebase in parallel for this kind of flow.

I’m here wondering how anyone could work on several tasks at once at a speed where they can read, review and iterate the output of one LLM in the time it takes for another LLM to spit an answer for a different task.

Like, are we just asking things as fast as possible and hoping for a good solution unchecked? Are others able to context switch on every prompt without a reduction in quality? Why are people tackling the problem of prompting at scale as if the bottleneck was token output rather than human reading and reasoning?

If this was a random vibecoding influencer I’d get it, but I see professionals trying this workflow and it makes me wonder what I’m missing.

Post reply on HN