A lot of this university research on AI feels dated. This is something we all faced months ago. Many times they're also reaching conclusions using obsolete models, etc. Feels like things move too fast for traditional research cycles to catch up to AI dev
The problem is that when nobody writes code or feels ownership over it anymore, nobody will be qualified to or really interested in doing the code reviews. The way forward could involve dropping code reviews altogether. You could argue that the useful pingpong between coder and reviewers has been replaced by the similar pingpong between the prompter and the agent.
In my company, people found out that if they use an agent that commits and do the pull/merge request, they can approve it themselves and bypass a second set of eyes.<p>Since they are the one doing the prompting, they quickly got lazy of actually reviewing the output from the LLM which means that nobody is reviewing anything.<p>It hasn't happened yet but I guess that is how you end up with major outages.
That would be great, IF there were valuable ping-pong between the prompter and the agent. For skilled engineers the game between themselves and the agent is enough. But most people are submitting senseless slop grenades for review.<p>Claude always comes up with more things to add to the code that are pure bloat and become inbred bombs over several iterations, and some people can't distinguish what suggestions to reject and go along with everything Claude suggests to the detriment of the program #garrytangate
Maybe we should just review the prompt(s) the PR author used. Would be nice if this was automated and included in a PR. So code review is really checking that the inputs were valid, and testing the outputs.
This feels obvious to me, but it's interesting how so many people feel the opposite.<p>I guess it depends a lot on how a company manages their SDLC/bureaucracy
If someone doesn't think code review is the bottleneck, chances are they've got AI doing their code reviews too.
Harvard researchers found a tree in a forest
From real-world experience, I have to disagree. It always has been and continues to be a faulty, up-front specification problem. The tail don't wag the dog.
With all respect to your personal experience, I could not possibly disagree more strongly with this.<p>In my own real world experience, the bottleneck has never been crafting the perfect specification up front. In fact, I have never, not even once, seen the initial specification for any real world software project of any mentionable size or scale survive unscathed to delivery. In reality, it is much like the old wartime maxim. "No Plan Survives First Contact With the Enemy".<p>The real world is messy and unpredictable. Every single software project of significance that I have been a part of has always involved testing, validating, and reworking the assumptions in the initial design and spec, refining them to arrive at the final product.<p>Furthermore, this iterative process (pre-AI) used to involve one or more humans following the development story and understanding what design changes and corresponding trade-offs were happening along the way (and why they were being made). By the time there was a finished deliverable ready for review, the person involved was privy to the story of why the development shaped up the way it did. They were able to account for the big picture, adapt accordingly along the way, and be able to explain why things ended up the way they did.<p>IME, with fully-agentic PRs, AI tends to view the specification as gospel and to view every point of friction between the specification and the real world as something to be worked around or minimized. Where a real human would pause, zoom out, and consider the system and bigger picture, considering what design changes might be needed, the AI will assume that its job is to make the specification a reality at all costs.<p>You can of course mitigate this by staying more closely involved with the work as it's being done, but this is of course slower than just throwing a spec over the wall and letting an agent run with it. It seems that people are far too eager to optimize for raw speed, and not nearly concerned enough with correctness or human understanding.<p>A sister comment mentioned a plethora of PRs that don't solve the right problem. If you are swamped with PRs solving the wrong problem, the root cause is not that you didn't foresee every future possibility or undiscovered devil in the details in order to create the right spec, the problem is that you thought you could come up with the right prompt at the outset and that an agent living in a clean digital world could make the journey all the way to a product fit for the messy real world on its own.
Very true. Which makes the conclusion reached be this study even worse: we are stuck reviewing endless PRs that solve <i>the wrong problems</i>.
I don't fully disagree with you. That is a real big problem.<p>But both things can be true. One problem doesn't exclude the other.
> The tail don't wag the dog<p>If I increased the output of my pump jack and identified the refinery as the new bottleneck would you say the same pithy thing? <i>NB</i> a single pump jack can pump different grades of crude oil at the same time.
You may need to check the pipeline so that the refinery isn't stuck filtering random stuff from the oil.<p>AKA, it would be nice to have nice patches like this one to review.<p><a href="https://cgit.freebsd.org/src/commit/?id=09d62ba33de113d01e889f5f8a5a8db071fba91e" rel="nofollow">https://cgit.freebsd.org/src/commit/?id=09d62ba33de113d01e88...</a>
So the solution is: write a perfect spec and then you'll have perfect code, no need for reviews?<p>What world do y'all live in where this is your reality?
That's sort of old news. Code isn't manually reviewed anymore much.
Test don't review.
What about design decisions or code quality? Tests don't cover those.
Equally time consuming and mind-numbing, IMO.
That bottlenecks too, in startup ahead of the adoption curve the whole cicd pipeline down to how to merge is being rethought
This again increases the demand for good programmers.
Write only programmers are dime on dozen. Those who can read code written by others (and themselves) and analyze it are harder to find.
No pull request in my company get any human review comments anymore. No one is reading.
I've submitted the original paper (<a href="https://fion.ac/jellyfish.pdf" rel="nofollow">https://fion.ac/jellyfish.pdf</a>), but others already have to little engagement, likely due to the paper's terrible title.
I really think ‘shifted the bottleneck to code review’ is misleading. It’s bad code. They write bad code. Yes if you want to salvage it you do a lot of code review, but that’s only because you’ve set your process up to pick spaghetti off the wall against which it has been flung. You could easily just push it all live without review and then pretend the bottleneck is SRE time, or set fire to yourself and claim the bottleneck is emergency service response time. But the root cause is that it’s bad code.
Vaguely reminiscent of the classic trope around 70's computer "effficiency gains" where a newly introduced computerised accounting system would end up taking longer than the original human-run system because once the computer was through doing the books the original human bookkeeper must still check the results manually.
"code is cheap"...if you don't need to understand, review, and maintain it as part of a team.
I have never heard of the term Job Market Paper (JMP) but this is the second one I saw on HN in two days. The other one is this<p><a href="https://news.ycombinator.com/item?id=50516245">https://news.ycombinator.com/item?id=50516245</a><p>Guess I have to ask AI.
We needed a research paper to tell us this?
Just because it is obviously true to you, it doesn't mean it is obviously true to others.<p>And just because it is obviously true to you, it doesn't mean that it is true, either.
And just because harvard researchers say something doesn't make it true either. Especially when it's like 6 months late and reviews are probably not the bottleneck anymore - testing, ci, parallelization are (imo).
A <i>Havard</i> research I'll have you know! /s
do you even have a PhD?<p>(/s)
I'm being told the answer is simply to let AI review and merge the code. Problem solved.
Harward researcher read lovable blog post
But people keep saying "coding was never the bottleneck!".
In other news, Dartmouth researchers find the sky is blue.
[flagged]