A bit tongue-in-cheek but I'm amazed by people that don't open an IDE or look at code. Are you paid to press enter at anything that Claude present to you?

Personally I usually use Claude inside the Jetbrain's IDE terminal, even if I code by hand obviously less. I still like using the diff, navigation, quick access to any file path for my prompt etc but maybe that won't last.

(edit: although I currently use an old perpetual fallback license because I didn't like the last price increase especially as they slowly remove what I like in the UI)

▲

fg137 6 minutes ago | parent | next [-]

You will be surprised by how many professional software engineers don't read their code or care these days.

I have seen a bubble sort function in a PR from an engineer with 20 years of experience. Meanwhile sort from standard library is easily available with one single line.

The bar has become as low as "it works" without considering what's in the code or whether the entire feature should even exist at all.

P.S. that same engineer sent out a PR of 200-file feature. The PR is so large that it freezes the latest MacBook Pro if you try to read it. Nobody reviewed it and he merged it himself. Nobody uses that feature, and nobody in the teams wants to maintain it. Now we are considering scrapping it.

▲

etothet 6 minutes ago | parent | prev | next [-]

Related, it amazes me how many seasoned developers don't know how to do basic tasks in their editor/IDE with the keyboard and instead rely on their mouse. Most people don't need to be super users, but it baffles me when I see a developer who hasn't at least learned the keyboard shortcuts for opening files and jumping to functions/methods, etc.

▲

patwolf 41 minutes ago | parent | prev | next [-]

I used to use Claude inside of a terminal within Webstorm until I realized I rarely looked at the code in the IDE. Instead I was creating draft PRs and reviewing the code in github. Now I use claude inside of herdr, and I appreciate having more screen real estate devoted to claude. As a long-time Jetbrains subscriber it pains me to stop using it. But at this point, I'm not sure what they could come up with that would be compelling enough for me to switch back.

	▲	cmrdporcupine 34 minutes ago \| parent [-]
		Their coding agent "Junie" is actually really good. The problem is they force you through only a few curated models. And try to funnel you through them to subscribe to do it, too. It's not like Pi or opencode that lets you just point at an OpenAI API endpoint and then choose whatever model. If I recall you can even actually use local models, or openrouter etc, but only use the specific model variants from their curated list. It's insane. They tried to stick themselves in the middle, and failed. Nobody will use it. They've also done so many pivots on AI, all of them weakly and annoyingly done. They couldn't even pull of FiTM copilot well, they were super late on it and it had all sort of bugs. They could have just taken the loss and written an amazing GUI coding agent that integrated well with their IDE -- amazing integrations with their refactorings, etc. -- but that played well in other people's ecosystems but they refused and tried to own the whole pipe. Or something. They just confused me. Their latest attempt is to allow you to connect to and run other people's agent harnesses inside the IDE and it works well enough but it wasn't enough to grab me since I (like you) use herdr on another machine to do the coding. I've been using their products since ~IDEA 3.x. Almost my entire 25+ year career really. My fingers are wedded to their keystrokes.

▲

lnrd 9 minutes ago | parent | prev | next [-]

Personally I don't use CLI anymore, Codex app is very good and it starts to look like how IDEs will be in the future. You can review code in a GitHub style diff and leave inline comments (super useful), have multiple agents work in parallel with or without worktrees, plus there is very good code navigation (especially if you ask followup clarification questions that will link to other parts of code).

▲

bsoqk 40 minutes ago | parent | prev | next [-]

>Are you paid to press enter at anything that Claude present to you?

I'm paid to create a product. If Claude does so without me having to look at the code, then that's what I'm being paid to do.

▲

lemagedurage 12 minutes ago | parent [-]

You could be implicitly paid to understand what you're delivering and reading code could be a way to achieve that.

	▲	etatester 4 minutes ago \| parent [-]
		I think you're paid to deliver. Lots of developers for decades have delivered crap that looks good on the surface and is otherwise unmaintainable. Now we're reaching the point where "everyone can code" and review queues are getting too long, with the result of many PRs being yoloed. This of course varies by company but this is clearly where it's headed: bot pushes, bot reviews, you look at the PR title and click merge.

▲

sporedro 14 minutes ago | parent | prev | next [-]

I’m sure there are people who aren’t looking at the code at all. But for those that are I guess I’m wondering why bother with an IDE anymore? I’m finding I can just review everything I need to with a text editor like Neovim now. Even GitHub review is probably good enough for people.

▲

ivanjermakov 15 minutes ago | parent | prev | next [-]

JetBrains still has best tooling for previewing changes, resolving conflicts, git integration. I get that vibe coders not necessarily need all that but it's the best class tooling money can buy.

▲

user43928 41 minutes ago | parent | prev | next [-]

Using a CLI coding agent in your IDE's terminal is a terrible way to view conversation history and works poorly for organizing multiple conversations.

It only fits a hands-on, merely AI-assisted development approach, on one feature at a time, that is not typically productive compared to agentic development.

You might disagree, but you'll find that the proponents of the hands-on approach are losing ground every month as AI gets better at working autonomously.

	▲	lemagedurage 7 minutes ago \| parent \| next [-]
		I'm expecting IDEs to adapt to new workflows, albeit very slowly. There is potential to build a better UI than what's constrained within a CLI's grid of characters.
	▲	conradfr 33 minutes ago \| parent \| prev \| next [-]
		I'll admit I'm currently not up to speed on having multiple features worked at the same time, with git worktrees etc.
	▲	surgical_fire 18 minutes ago \| parent \| prev [-]
		Except surrendering cognitive control over the system being built makes things worse. Claude constantly makes poor architectural decisions, adds unnecessary and costly checks, makes wrong assumptions, etc. Doesn't take the value out of LLMs writing code, but they need to be properly steered and reasoned with. How will you do so if you don't even browse the code it generates. I always suspect that the people all in fully agentic codig like this are mostly creating prototypes, half-assed copies of existing products, etc. I am glad to not work in such an environment.

▲

cedws 22 minutes ago | parent | prev | next [-]

What do you expect when management pressures engineers to tokenmaxx? This is a product of their doing.

▲

ipsod an hour ago | parent | prev | next [-]

I'm paid to produce software that has features and works.

Nobody cares how I get there or how ugly the code is. They care how fast I can do it and how reliable the software is.

I look at code sometimes, in down time, to see what's been done terribly by AI, and to fix it and hopefully fix the process so that things don't get done terribly in that particular way in the future.

▲

poncho_romero 40 minutes ago | parent | next [-]

It's not about "how ugly the code is". Poor solutions heaped on top of poor solutions can result in a system with real users and intractable issues. I'm all for AI, but not reviewing the code seems likely to cause issues long term.

	▲	ipsod 28 minutes ago \| parent [-]
		Well, I used to pay more attention to the code, and then I found that if I spent more tokens having the AI review its work than actually creating new features, I was able to get more, better work done. The AI review stage is where I've found prompting matters a lot more than that initial prototyping phase. I've iterated on prompts and tooling that help the AI keep the codebase clean-ish.

▲

swozey 41 minutes ago | parent | prev [-]

Whats your YOE, like when did you enter tech as a SWE?

This shouldn't be normalized for you yet unless you're at a faang pushing this at the edge and new to the field, cause this isn't what we used to do 2 years ago.

If you're happy with the ai slop $$$ job more power to you but that isn't the entire field and there used to be (and hopefully still are) good and fun engineering jobs.

Contrary to popular normie belief, no not everyone wants to work at the Metas and OpenAIs and for good reason.

	▲	ipsod 10 minutes ago \| parent [-]
		YOE is ~30, from my first PHP app to present. I've spent somewhere between 5 and 80 hours a week coding for the past 30 years, mostly self-employed, writing tools and creating custom CNC machines/robots for my own business, but more recently doing same thing for a company. I still get to do some coding, where there are safety-critical production systems, but the work is mostly tooling that gets us to that point or supports the business otherwise. It's an awesome job. Couldn't be funner, pretty much, except on data collection days. I get high level tasks, or come up with my own, and find or build solutions - no more running a whole business, doing production, keeping books, shipping orders, doing customer support - I only do the stuff I like.

▲

vel0city 37 minutes ago | parent | prev [-]

When you give a ticket to a jr developer, do you look over their shoulder the entire time they write the code? Or do pause to answer questions, give feedback on how to go about a task, and review their results?