Surviving Code Reviews in the era of AI

在 AI 时代幸存的代码审查

My coworkers are all fully AI pilled. As a consequence, every PR that comes my way for review is on average ~6k lines of diff. 我的同事们现在全都沉迷于 AI。结果就是，我收到的每一个待审查的 PR（合并请求）平均都有约 6000 行的代码差异。

It’s well established that even PRs an order of magnitude smaller than this are too big to be effectively reviewed. 众所周知，即使是规模比这小一个数量级的 PR，也已经大到无法进行有效审查了。

I’m still clinging to the idea that us humans should understand how the systems we are building work, so I’m hesitant to use AI for reviews aside from more general question answering. 我依然坚持认为，我们人类应该理解我们所构建的系统是如何运作的，因此除了进行一些通用的问答之外，我很犹豫是否要使用 AI 来进行代码审查。

Much of what it produces in the way of explanations are difficult to follow and overly verbose anyway. 况且，AI 生成的解释大多难以理解，而且过于冗长。

I’m sure I’m not the only person here who has been dealing with this problem, so I’m curious if anyone here has found any strategies (organizational or personal) which have helped weather this maelstrom. 我相信我不是这里唯一一个面临这个问题的人，所以我很好奇，大家是否找到了什么策略（无论是组织层面的还是个人层面的）来帮助应对这场混乱。