Given the increased use of AI, my experience is that teammates are moving so fast churning out so many changes that it is nigh impossible to review it all. I can't even keep up with the code being generated by my own use of LLMs at times. Granted, I can slow it all down. And I do at times when one of the following is true:
1. It is a new space I want to understand
2. I don't trust the agent for the current domain
3. It is incredibly complex and nuanced work
Leaning on oracles (something that can provide a ground truth that LLMs can check their impls against) gives a lot of confidence and eases my mind when skipping reviews. Expansive testing and formal verification seem like they will displace code review.
Code review also provided mentorship, design feedback, shared ownership. Where is mentorship being redirected? Are people still finding time to design review?
Open Source AI assisted 1k+ line PRs is a whole nother ball of wax. My best trick here is to extract the key ideas from the PR and re-implement it myself.
0 comments
—
Ask HN: What has been the fate of code review? · HackerTrans
Leaning on oracles (something that can provide a ground truth that LLMs can check their impls against) gives a lot of confidence and eases my mind when skipping reviews. Expansive testing and formal verification seem like they will displace code review.
Code review also provided mentorship, design feedback, shared ownership. Where is mentorship being redirected? Are people still finding time to design review?
Open Source AI assisted 1k+ line PRs is a whole nother ball of wax. My best trick here is to extract the key ideas from the PR and re-implement it myself.