在人工智能时代的评审
你们如何确保投入生产的代码质量高，尤其是在代码审核所需时间显著超过代码生成时间的情况下？<p>在生成代码的人员与审核人员之间存在巨大的不对称，使得审核过程比以往更加困难。<p>我在想，是否可以考虑不再审核拉取请求（PR），而是转向审核计划，以确保在至少有另一人批准计划之前，不生成任何代码。<p>一旦代码生成，参与计划的用户仍然可以进行审核，但由于双方都参与了计划，这应该有助于减少不对称性。<p>感觉我们需要一种方式来协作和迭代计划。希望听听你们对此的看法。
查看原文
How are you guys ensuring that the code that goes into production is high quality now that the time to review code is significantly greater than the time to generate it.<p>There is a huge asymmetry between who is generating the code and who is reviewing it, making the review process even more painful than it used to be.<p>Wondering whether if instead of reviewing PRs, we should instead move towards reviewing plans so that no code is generated before at least another person approves the plan.<p>Once the code is generated, the users who contributed to the plan can still review it but the fact that both participated in the plan should help reduce the asymmetry.<p>Feels like we need a way to collaborate and iterate on plans. Would love your thoughts on this.