Earlier quoted context omitted.
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.
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.
GPT-6 Astra in code review: Gains, privacy, and cost
21–30 of 80 posts
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#22Earlier quoted context omitted.
1. Whether the thing should be done in the first place 2. If it's the correct solution on a high level 3. Whether it conflicts with or duplicates other parts of the system 4. Whether the comments are actually useful or restating the LLM chat Also many others but these are the most common IME
All of these are angles an AI reviewer can test for as well, and will (IME) mostly catch mistakes correctly. I also still manually review code, and usually also catch issues, but the severity of what I find shrinks ever further as agents get better. The sprawling code comments are becoming the most draining part of code review though, that's really killing me from the inside.
If you don't master this for your own project, what's even the point of your job.
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#23Astra 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.
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#24Comparison 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't worth the "noise" and friction it causes developers during C/I code review
Code generated these days with fable and sol are near perfect. What issues they might have is logical errors.
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#25Comparison 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't worth the "noise" and friction it causes developers during C/I code review
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.
If you're doing a simple CRUD app, sure.
If you'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.
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#26Re: GPT-6 Astra in code review: Gains, privacy, and cost
#27Earlier quoted context omitted.
1. Whether the thing should be done in the first place 2. If it's the correct solution on a high level 3. Whether it conflicts with or duplicates other parts of the system 4. Whether the comments are actually useful or restating the LLM chat Also many others but these are the most common IME
All of these are angles an AI reviewer can test for as well, and will (IME) mostly catch mistakes correctly. I also still manually review code, and usually also catch issues, but the severity of what I find shrinks ever further as agents get better. The sprawling code comments are becoming the most draining part of code review though, that's really killing me from the inside.
No, none of today's AI would give you enough signal around "should this thing be built in the first place" nor if it's the correct solution on a high level.
They don't understand why you are doing what you are doing, and even if you explain it, they still don't actually understand the motivation and lots of other things.
You'll get them to do guesses and pretend they actually know how to prioritize and will tell you it makes lots of sense, whatever they come up with. But try following it blindly and you'll see where you end up.
This is why "one agent + one good developer" beats "thousands of agents working in a swarm" still today.
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#28In 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'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's your experience and context ? What do you do ? What works for you what doesn't ?
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#29Both OAI and Anthropic seem to have released a model that is slightly better but cost ~2x the previous iteration. Interesting play
Re: GPT-6 Astra in code review: Gains, privacy, and cost
#30How 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've just been handed a burst of stacked PRs amounting for ~15k LOC b…
have him start with an overall design doc if his change is 15k, it'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's 15k LoC no one is truly familiar with, even if you do try to review it