undefined | Better HN

0 pointstibbar1mo ago0 comments

the problem with LLM code review is that it's good at checking local consistency and minor bugs, but it generally can't tell you if you are solving the wrong problem or if your approach is a bad one for non-technical reasons.

This is an enormous drawback and makes LLM code review more akin to a linter at the moment.

0 comments

menaerus1mo ago

I mean if the model can reason about making the changes on the large-scale repository then this implies it can also reason about the change somebody else did, no? I kinda agree and disagree with you at the same time, which is why I said most of the engineers but I believe we are heading towards the model being able to completely autonomously write and review its own changes.

tibbarOP1mo ago

There's a good chance that in the long run LLMs can become good at this, but this would require them e.g. being plugged into the meetings and so on that led to a particular feature request. To be a good software engineer, you need all the inputs that software engineers get.

menaerus1mo ago

If you read thoroughly through Stripe blog, you will see that they feed their model already with this or similar type of information. Being plugged into the meetings might just mean feed the model with the meeting minutes or let the model listen to the meeting and transcribe the meeting. It seems to me that both of them are possible even as of today.

j / k navigate · click thread line to collapse

0 pointstibbar1mo ago0 comments

This is an enormous drawback and makes LLM code review more akin to a linter at the moment.

0 comments

menaerus1mo ago

tibbarOP1mo ago

menaerus1mo ago

j / k navigate · click thread line to collapse