In our brave new world of remote work, asynchronous methods of collaboration have become essential. When you’re working in different locations—or even different time zones—you need communication tools that allow you to send a message and move on. The idea is simple: you deliver a message, and whenever the other person has a moment, they’ll respond, then continue with their own work. No one’s blocked, and no one is forced to interrupt their focus to keep someone else unblocked. The alternative would be intolerable: waiting hours, or even days, for responses, or stopping whatever you’re doing to reply immediately just to avoid holding someone up.
在我们勇敢的远程工作世界中，异步的协作方法已经变得至关重要。当您在不同的位置（甚至不同的时区）工作时，您需要允许您发送消息并继续前进的通信工具。这个想法很简单：您传达信息，只要对方有片刻，他们就会做出回应，然后继续自己的工作。没有人被阻止，没有人被迫打断他们的注意力，以使别人没有阻碍。替代方案将是无法忍受的：等待几个小时甚至几天，以进行回复，或停止您立即做出回复，以免避免将某人抬起。
There are, of course, times when quick responses are necessary, but if you frequently feel blocked, there may be underlying project management issues. Is your manager simply assigning tasks one by one, without giving you a broader sense of direction? Is your organization failing to consolidate on-boarding and reference materials, leaving you hunting for answers instead of finding them documented? Regardless of the cause, people need the ability to work independently without constant guidance.
当然，有时需要快速响应，但是如果您经常感到被阻止，则可能存在潜在的项目管理问题。您的经理是否只是一个一个人分配任务，而不会给您更广泛的方向感吗？您的组织是否无法合并登机和参考材料，而是您寻找答案而不是找到记录的答案？无论原因如何，人们都需要在没有不断指导的情况下独立工作的能力。
Assuming you’re able to code independently most of the time, and have good asynchronous ways to communicate with coworkers, there’s still one big hitch: code reviews. For teams striving to work asynchronously, code reviews can be a serious roadblock. When a piece of code is ready to deploy, it often grinds to a halt, waiting for review. Progress stops cold. Blocking the pipeline with a manual approval step can mean days of waiting for someone to sign off on it. Sure, you could pivot to another project, but context switching is costly. When you’re on a roll with your highest-priority item, getting stopped by a code review is about as inefficient as it gets.
假设您大部分时间都可以独立编码，并且具有与同事交流的良好异步方法，那么仍然有一个大型障碍：代码评论。对于努力进行异步工作的团队，代码评论可能是一个严重的障碍。当一块代码准备部署时，它通常会停止，等待审查。进度停止了冷。通过手动批准步骤阻止管道可能意味着几天等待某人签字。当然，您可以转移到另一个项目，但是上下文切换成本很高。当您使用最高优先级的物品滚动时，被代码审查阻止的效率与其效率低下。
The real issue here is that code reviews aren’t reviews at all—they’re approvals. “Review” implies that something is complete and you’re looking it over after the fact. But what we call a “code review” today is more of a gate-keeping process, where the code is almost done, and someone has to give it a green light. It’s not simply getting a second opinion; it’s waiting for permission, holding up the flow while work sits on the sideline. If it were a true review, you’d be able to push your code live and get feedback afterward. Instead, you’re stuck, watching as progress slows.
这里真正的问题是，代码评论根本不是评论，而是批准。“评论”意味着某件事已经完成，事实后您正在查看它。但是，今天我们称之为“代码审查”的是一个守门过程，几乎完成了代码，并且有人必须给它一个绿灯。这不仅仅是获得第二意见；它正在等待许可，在坐在边线上的工作时保持流动。如果这是一个真实的评论，您将可以直播代码并获得反馈。取而代之的是，您被卡住了，看着进度的速度。
Imagine this alternative setup: you deploy your code, and a notification goes out letting someone know there’s something new to review. At their next opportunity, when their mind isn’t deep in another problem, they can look it over. In the meantime, you’re able to keep moving on your next task.
想象一下此替代设置：您部署代码，并发出通知，让某人知道有一些新的要审查。在他们的下一个机会中，当他们的思想在另一个问题上没有深入的境地时，他们可以看一下。同时，您可以继续执行下一个任务。
I know this idea might give some managers heartburn, but it doesn’t have to. If a problem does slip through, it can be addressed in a future commit, which would go live faster since it isn’t waiting on a review. For serious issues, a basic smoke test could automatically catch and roll back errors. And let’s be honest—a robust test suite is likely to catch issues more reliably than a human reviewer. Wouldn’t time spent on manual reviews be better invested in building more comprehensive tests?
我知道这个想法可能会给一些经理烧伤，但这并不是。如果问题确实解决，则可以在将来的提交中解决，因为它没有等待审核，这将更快地直播。对于严重的问题，基本的烟雾测试可能会自动捕获和滚动错误。老实说，强大的测试套件可能比人类评论者更可靠地发现问题。在制造更全面的测试上，是否会更好地投入到手动评论上的时间？
Ultimately, code reviews should empower us to keep moving, not hold us back. By shifting from code approvals to genuine code reviews, we can create a workflow that prioritizes progress and learning without unnecessary delays. Embracing a post-deployment review approach allows us to maintain momentum, foster independence, and focus on building reliable tests that catch issues before they reach production. Let’s make code reviews a tool for growth, not a bottleneck.
最终，代码评论应授权我们继续前进，而不是阻止我们。通过将代码批准转移到真正的代码评论，我们可以创建一个工作流，该工作流程优先考虑进步和学习，而无需不必要的延迟。接受采取部署后的审查方法，使我们能够保持动力，促进独立性，并专注于在达到生产之前捕获问题的可靠测试。让我们将代码评论成为增长的工具，而不是瓶颈。
