News for hackers. Stuff that matters.
Re:How the Claude Code team does code review by stillpointlab on Friday October 16, 2026 @04:26PM (#50124141)
Issue: I am still unable to stop myself from doing line-by-line code review

Response: Try experimenting in a low stakes environment

From Google: "Exposure therapy is a psychological treatment designed to help people confront their fears, break cycles of avoidance, and reduce anxiety."

Re:How the Claude Code team does code review by g-b-r on Friday October 16, 2026 @04:56PM (#50124561)
The thing is that's not an issue in the slightest, it doesn't need therapy!!

It's those who don't do it who'd need a talk..!

Re:How the Claude Code team does code review by stillpointlab on Friday October 16, 2026 @05:35PM (#50125082)
I think that depends on where you work. If your company demands that all code is reviewed then anyone who doesn't do that should be spoken to.

However, I suspect there are teams that are making different choices. In the most obvious example, I can do whatever I want on my personal projects (I hope you agree). And if I started a business and hire in programmers, I have some expectation on defining the culture, making hiring decisions based on my preferences, etc.

Whether or not such teams succeed will be a matter of fact, which I do not believe has been decided at this time.

Re:How the Claude Code team does code review by 9dev on Friday October 16, 2026 @05:12PM (#50124808)
I hate to say this, but you're now living in a world where the value of artisanal code is rapidly approaching zero. If you still cling to beautifully written code as your core qualification, you're having a rough future ahead of you.

And I say this with the bitterness of someone having lost a big part of what made me enjoy this line of work.

Re:How the Claude Code team does code review by g-b-r on Friday October 16, 2026 @06:14PM (#50125467)
That's not wrong right now, we'll see in the future.

But I have no interest in working as a vibecoder, there are many other jobs that I'd enjoy more

Re:How the Claude Code team does code review by troupo on Saturday October 17, 2026 @03:07AM (#50128682)
Re:How the Claude Code team does code review by troupo on Friday October 16, 2026 @05:10PM (#50124771)
No. The issue is: "I notice too many things (redundant code, duplicate code, overly complex architecture, etc.) during review"

How does "low-stakes environment" fix that?

Re:How the Claude Code team does code review by stillpointlab on Friday October 16, 2026 @05:29PM (#50125028)
Because one may learn that those fears are overblown. Or they may learn that they cannot build any kind of software without reviewing every line of code.

The person is saying "I am still unable to stop" and that is most likely because they feel a sense of responsibility. If they choose a project where there is no responsibility, where it literally doesn't matter if the project fails, they may feel able to stop. And if they manage to make that project work, if they can succeed, then they will build up confidence.

It seems better to be able to work both on projects where they review all code as well as projects where they do not review any code. In fact, keeping their job in the long term may (or may not) require having both skills.

Re:How the Claude Code team does code review by daveguy on Friday October 16, 2026 @06:26PM (#50125594)
yolo'ing a code complexity generator doesn't make it suddenly stop being a code complexity generator.
Re:How the Claude Code team does code review by troupo on Saturday October 17, 2026 @03:06AM (#50128677)
> one may learn that those fears are overblown.

They are not overblown. LLMs do all the things the person described.

> Or they may learn that they cannot build any kind of software without reviewing every line of code.

We already had bad horrendous software before the onslaught of LLM-slop. Why contribute to that?

> And if they manage to make that project work, if they can succeed, then they will build up confidence.

Confidence in what? It doesn't fix the underlying issue. And the underlying issue isn't "I can't stop" but "redundant code, duplicate code, overly complex architecture, etc." that LLMs regularly produce.

> It seems better to be able to work both on projects where they review all code as well as projects where they do not review any code.

"If I close my eyes maybe this goes away"

Re:How the Claude Code team does code review by jazzyjackson on Friday October 16, 2026 @05:29PM (#50125027)
I guess they’re just saying “you’re holding it wrong”

Last time I chose to vibe code, I did it in a language I didn’t know so that I wasn’t tempted to try and comprehend the choices the robot made. I ended up with the application I wanted.

Caveat: it was code I would never have to touch again, I ran a script to generate the 140,000 static html pages that the rails app provided and then just uploaded them all to R2 buckets (million reads per month on free tier)

Re:How the Claude Code team does code review by troupo on Saturday October 17, 2026 @03:06AM (#50128679)
> I guess they’re just saying “you’re holding it wrong”

No, they are saying "who cares if all those issues with code are true, just don't review it"

> Caveat:

It's not really a caveat. I also have throw-away code. But we're not talking about throw--away code. We're talking about the systemic issues in LLM-produced code, which are completely ignored and the answer is always "who cares, close your eyes and don't review the code".

Re:How the Claude Code team does code review by jazzyjackson on Saturday October 17, 2026 @01:23PM (#50133039)
Right. You don’t review the machine code or the interaction with registers and branch prediction. If the behavior matches the desired outcome what does it matter?

The classic consideration is, this code will need to be maintained, built on top of… but it’s not like that was ever a solved problem, big projects remain fragile and corporate turnover means no one knows the entire stack. So I see the vibe code out there as just another imperfect way to build barely good enough software.

I’ve also written code I built slowly and intentionally as a piece of art, beautiful code I was proud of. Didn’t make me any money :)

Re:How the Claude Code team does code review by troupo on Saturday October 17, 2026 @01:56PM (#50133342)
Ah yeah, the good old "you don't check compiler output" argument.

LLM output isn't compiler output. It's a lot of shitty code that contains duplication, subpar algorithms, bad data access patterns etc. We were complaining about awful software before LLMs. Why is it now absolutely okay to write shitty software just because it's LLMs?

Also: literally no one is talking about "writing software as art". We 're talking about this: "many things (redundant code, duplicate code, overly complex architecture, etc.)"

Re:How the Claude Code team does code review by jazzyjackson on Sunday October 18, 2026 @01:31AM (#50138172)
My point wasn’t that compilers are just as bad as LLMs, but that whether humans or robots are writing code, it’s still going to be Just Good Enough to ship.
Re:How the Claude Code team does code review by troupo on Sunday October 18, 2026 @05:03AM (#50139296)
How do you know it's "Just Good Enough" to ship? I will repeat: We were complaining about awful software before LLMs. Why is it now absolutely okay to write significantly more shitty software just because it's LLMs?

For example, for all the claims of how LLMs are better than humans, or how you can ship gazillion LoC easily, we've yet to see any significant number of actual good software to come out of this slopathon. Even the frontier labs with unrestricted access to their own models who boasting how they merge 30000 PRs per day [1] ship unbelievable buggy shit. But it's okay because it's LLMs who cares?

[1] https://claude.dev/blog/solving-code-review-at-anthropic/