Hacker News new | past | comments | ask | show | jobs | submit
I find it extremely exhausting. And the better the AI code gets, the more tempting it is to do a very shallow review or skip it entirely. In the end, it's very similar to dealing with offshore teams. You spend an enormous amount of time and energy on writing specifications and you spend a lot of energy on code reviews. If you don't do that, it's very likely the project will slowly go off the rails.

I have no idea how the Linux maintainers do that job over a long time.

> I have no idea how the Linux maintainers do that job over a long time.

They're basically the lords of their subsystems. If something does not fit the project's vision and their own standard, it's unlikely to get merged. Imagine if you had the authority to dismiss PRs the same way and send the author back to the drawing board? But that's unlikely to happen as you'll be seen as a "bottleneck" by your managers.

loading story #50543732
loading story #50542188
Nobody understands the code any more. LLMs always take the long route. This is exactly what Dario wants. You can now only change code with an LLM.

> And the better the AI code gets

It doesn’t really get better. Since Opus 4.6, it’s maybe slightly better for code.

loading story #50543656
I do shallow reviews and it's working out fine. As long as I understand the schema and type changes and can glance at any new abstractions (rarely is any with my set up) then that tells me 80% of what I need to know in minutes.

A lot of this is codebase and app dependant. For the majority of business aps, if you have a well architectured codebase with clearly defined ways of doing things, you really shouldn't need much code review at this point. Every time you spot a gap you create an audit script to further enforce particular patterns/behaviours.

loading story #50544018
> slowly go off the rails

We're talking months here, not years. That isn't "slowly".