News for hackers. Stuff that matters.
Re:How the Claude Code team thinks about verification by xnorswap on Tuesday November 17, 2026 @09:09AM (#50531596)
I suspect that an ever increasing number of tickets being raised are being raised by agents themselves, nitpicking and being unable to deal with the idea of implementations having trade-offs.

It doesn't take 5 minutes to prompt claude, "Please pick up Ticket #1234567".

With modern models, you rarely need much more than that. Perhaps checking in an hour later with a quick prompt, "Progress report?" if it's still working on it.

Claude having written the ticket in the first place, defined acceptance criteria. Perhaps a human has skimmed it for a go/no-go decision, perhaps not.

The point is that at that scale you can't humanly read the code, so you need to define verification strategies that work for the machine.

Precisely so that you're not just running on pure vibes.

Re:How the Claude Code team thinks about verification by skydhash on Tuesday November 17, 2026 @09:34AM (#50531934)
> The point is that at that scale you can't humanly read the code

Why is that scale needed in the first place?

Re:How the Claude Code team thinks about verification by xnorswap on Tuesday November 17, 2026 @09:59AM (#50532270)
I don't think it is, but I think it's something worth paying attention to.

With my skeptic hat on, it'll be interesting to see what happens when you look at their internal speed, in PRs/month vs the outward velocity in features and improvements actually shipped.

With my booster hat, it's something to learn from so I can better scale from juggling hand-reviewed claude sessions to a future it might be demanded I join at some point.

We're in a weird space in development, where the initial mechanical work that used to take a week now takes an hour at most, but what remains is a lot of manual verification and developer-testing.

If we can learn from what these mega-swarms are doing to reduce the need for manual developer testing ( because at that speed it's clear there must be close to none ), then that is a useful lesson that might reduce our work per task too and let us do more.

And yes, some of that may be stuff we've known for years, such as functional CI/CD, better linting, better automated e2e testing with playwright, etc.

But actually convincing management to invest in that kind of thing isn't always easy, especially if it risks instability of a process that from their perspective has been working fine for decades, even if that "process" is someone logging onto a server to manually fire off a script that was last touched 15 years ago.

So having talks such as this to point to is useful. You can show management an expert on a stage, and in some companies an expert on a stage can be weirdly convincing to management in a way that their own employees sometimes are not.

Re:How the Claude Code team thinks about verification by skydhash on Tuesday November 17, 2026 @11:01AM (#50533275)
> We're in a weird space in development, where the initial mechanical work that used to take a week now takes an hour at most, but what remains is a lot of manual verification and developer-testing.

I don't think the low speed of development was an actual bottleneck. Coding in the real world is actually a mix of mechanical typing and information gathering. The typing part is not that relevant as it's actually not much time to type in 500 lines of code (if you touch type) assuming that's the median size of PR. It is the gathering of information that is IMO crucial for the health of the software.

It's like robots in a chemical lab. You can probably build some mechanical apparatus that can mix whatever components you want. But you still need a scientist to design experiments and to check the result. And while you can help speed up some of the process, what's valuable is the knowledge that the scientist extract, not the amount of experiments being done.

This scale of work is only possible because there's no information gathering going on. Instead it's just busy work with wishes and prayers hoping to get a good result.

Re:How the Claude Code team thinks about verification by fg137 on Tuesday November 17, 2026 @09:48AM (#50532133)
While I have seen numerous tickets addressed by Claude/Codex in one shot with decent solutions, about half of their first implementation is completely wrong in the direction, is way over engineered/significantly expands the scope, or leads to very confusing or even incorrect user-facing behavior.

I can't see how I would be able to keep customers happy without actually reading the code and understand what it is doing.

Re:How the Claude Code team thinks about verification by rolosa on Tuesday November 17, 2026 @12:11PM (#50534616)
The argument that engineers like the one in question are needed because of their judgment, guidance, experience, etc. But on the other hand if their job is reduced down to "@grok review and fix issue #42069", every 5 minutes of their workday, then what value do they actually add? Why not just remove them from the equation? I'm saying that a developer who brags about doing 2000+ prs/day is effectively dead weight and brings nothing to the table.
Re:How the Claude Code team thinks about verification by senordevnyc on Tuesday November 17, 2026 @08:29PM (#50540719)
Well, she’s using the new tools available to us to pioneer these kinds of scalable software factories and using that process to build a very successful product.

It sounds like you’re doing things basically the way they’ve always been done.

Re:How the Claude Code team thinks about verification by magicalist on Tuesday November 17, 2026 @10:45PM (#50541606)
> It sounds like you’re doing things...

What sounds like that exactly? I don't see anything in the GP about what and how they're "doing things" one way or the other.

They're making an argument about someone's statements. Engage with the argument or don't, but don't make it weird like this.

Re:How the Claude Code team thinks about verification by senordevnyc on Wednesday November 18, 2026 @07:45AM (#50545644)
This comment: https://news.ycombinator.com/item?id=50531344

This is so far from engaging with how Lauren actually works that’s it’s barely worth even responding to. They’re describing a standard software engineer workflow as it existed decades ago. Lauren is playing on a totally different level, more successfully I suspect (though who knows because while she’s public, this critic is anonymous).

Re:How the Claude Code team thinks about verification by losteric on Tuesday November 17, 2026 @10:57PM (#50541700)
Maybe the value is in setting up that system and the skillset to know when to stop/sidestep/backtrack that mechanism?

Basically management I guess