I realize this is likely being facetious, but just in case - code reviews are so much more than just 'check the syntax and style of the code'. They check the intention, check the actual functionality, find issues on the larger scale that LLMs literally can't.
Yes, PRs start piling up because devs can vibe code them faster than they can be competently reviewed. This is a problem with the vibe code process, not the code review process.
I was being half facetious, yes. But wouldn't the invoker of the LLM be already doing a review in that case? It just feels a bit redundant, to have engineer one do a code review of LLM's work, and then have engineer two do the same review.
The business cost with PRs isn't the first review but another developer, it's the number of iterations on a pull request due to defects and change requests. The way I am trying to promote the use of LLMs with more junior developers in my team (I am the CTO) is to use AI-assisted tools (we used Windsurf and recently switched to Github Copilot) for a first pass, e.g asking the agent for a review and catching potential defect before involving the human reviewer.
This doesn't mean the human reviewer will need to spend less time reviewing, but potentially this PR will be merged faster with on average a lower number of iterations and improved code quality.
I do have in my team some senior developers that are excellent, and it's very very rare I catch an issue in their PRs (maybe 1 out of 50). But I also have greener developers for who the ratio is way higher (like 8 or 9 out of 10) and this means repeated context switching for the reviewers.
I was in Malaysia and used the toilet in my hotel room. The handle was broken and was just turning idly. Since I was leaving for dinner, I told the reception desk that it was broken. They told me it would need fixed right away.
I got back two hours later, check the toilet and it is still broken. Call the desk, they're sending an "engineer" right away. The guy comes in, goes to the toilet, I show him that the handle is just turning idly.
He looks at me, surrounds my shoulders with his arm and tells me "I will show you".
Proceeds to turn the handle the other way round and, tadaam, the water flushes...
There are two options for verifying your age on Discord - face scan OR uploading government ID. So some people may have uploaded their ID instead of doing the face scanning, for whatever reason.
For example if the face verification failed and you need to file an appeal which requires uploading government ID. That's likely sizeable number of users, especially since the breach happened shortly after the requirement was implemented and many existing users had to do it.
reply