They do catch important things but it’s really contextual. You can’t grab a model slap it on top and say code review . Hence a dedicated review tool is almost dead . Code review should be part of your pipeline and consume test results from the original task , open spec etc . If you do not have that code review will not help if you do , what is the point of task rabbit just slap &lt;your harness in the sandbox&gt; review against &lt;goal&gt;

What really important things are human reviews catching in your org?I just feel more and more like the effort invested in manual reviews is not worth it

Code review tools are designed for less organised dev teams that don’t do PRs and mandatory human reviews already.It is papering over a lower level of competency without having to invest in actual human oversight or real process improvement.

Yeah I personally don’t understand the point of AI code review tools all that much, as AI is already generating the code as well. All of these AI code review tools create so much noise, yet don’t catch the really important things.

You have a very interesting definition of &quot;perfect&quot;, then.

&gt; Code generated these days with fable and sol are near perfect.If you&#x27;re doing a simple CRUD app, sure.If you&#x27;re doing anything more involved they get the job done with dozens of shortcuts that bite you in the ass the moment you have on-call duty.Way too much code and repetition and hacks.Especially in GPU code, but also in other fields.

It does add lot of noise after a point you start ignoring the suggestions and findings.Code generated these days with fable and sol are near perfect. What issues they might have is logical errors.

Comparison was done in the scope of coderabbit AI code review tool, which sadly makes it practically irrelevant.My personal experience as a software engineer, and a former security researcher who did manual code audit, is that this code review tool has such poor results that it isn&#x27;t worth the &quot;noise&quot; and friction it causes developers during C&#x2F;I code review

We try to avoid reviewing AI-generated code and built our own testing framework and platform to make that possible.Our principle is that our tests should give us enough confidence to not have to look at the code (which ends up being true for most changes we make). The core thing that makes this possible is that we run our entire code and infra (including fakes for external dependencies) in isolated, forkable environments and write tests against that, so they are as E2E as can possibly be.The problem then shifts from reviewing code to reviewing tests and that&#x27;s why we built our own platform. We have a UI that can diff tests, so we know what changed, and a visual way to inspect what the tests actually did. A test could drive a browser like a user would, and in our UI we get a replay of that browser interaction to look at. The browser is talking to a real version of our backend, and the tests can perform assertions against the database and fakes and really anything in our system.

throw his garbage out, the time and effort taken to review that is magnitudes more than what it took to prompt it.have him start with an overall design doc if his change is 15k, it&#x27;s definitely worth a design doc.and then have his contributions reviewed in pieces of 200-300 LoC PRs.any other solution is trading stability and system knowledge, that&#x27;s 15k LoC no one is truly familiar with, even if you do try to review it

Invest in having a good test suite that validates the functionality introduced by that code. Also AI can review code in an adversarial way and apply those fixes (that ideally will keep the previous tests you did on green)

I have AI confirm the logic works as expected, but review for system design.Often in both web&#x2F;backend I’ve found AI to produce overly duplicative code, or have aspects that could be hard to maintain. Generally less due to the AI, and more because of the prompt itself.That and even if you’re going to AI slop it up, I’d still demand it be broken up into 1-2k LOC chunks or per meaningful “thing”. This also lets us gradually ramp the change to confirm it actually works earlier on

How do you guys review AI-generated code ?In our team, frontend work is vibe-coded by the PO and merged as-is without review. Backend is coded by developers, using AI but in a slower, more controlled way.Recently, our PO has been trying his hand at vibe-coding the backend. I must say he is a smart guy, almost technical but not quite a developer. We&#x27;ve just been handed a burst of stacked PRs amounting for ~15k LOC backend. We do not quite know what do to about it.I know we are not the only ones in the situation. What&#x27;s your experience and context ? What do you do ? What works for you what doesn&#x27;t ?

Generally speaking &#x27;the Fable&#x2F;Astra built GTA 6&#x27; videos are a new phenomenon, so it&#x27;s clear these models have new capabilities and people will need new ways of interacting with them if they want to leverage these imo.

That likely won’t change if other competitors don’t take the lead at some point. If companies are willing to pay top dollar for the best models AND they get to extract as much money from Chinese labs distilling Astra&#x2F;Fable it makes no sense to lower prices. Obviously not great for everyday users who don’t have unlimited money.

That should be expected based on the scaling laws that we expect; larger models are more intelligent and cost more. Now it&#x27;s very unfortunately that they don&#x27;t publish the size of their models.

I don&#x27;t know, in the Codex app, it burns the limit much faster.

Astra and Sol are the same price when you factor in token efficiency

Roughly how we price (high skilled) human labor.

Interesting comment because it is true that Astra is costlier for the same intelligence tasks as Sol.But this is not the same for Fable at all.

Both OAI and Anthropic seem to have released a model that is slightly better but cost ~2x the previous iteration. Interesting play

It&#x27;s a bigger model, of course it&#x27;s slower.

Astra seems to be really slow. Maybe it intends to read more context. But from my experience it is definitely slower than 5.6 sol when handling same tasks.

Given that Fable is a Sol-class model, should Astra not be compared to Mythos in those tests?

GPT-6 Astra in code review: Gains, privacy, and cost