It seems that today, with all of our tests, we allow the code to grow woolly and complicated in ways that, in the past, with no automated regression tests, we never could have tolerated. We were forced to keep the code simple because if we didn't, the complexity of the special cases wouldn't fit in our heads. This leads me to the following idea, which I will dig into in the rest of this article: Software teams need a healthy balance of both intellectual control, which comes from reasoning, and statistical control, which comes from testing. Complexity is the enemy of reasoning; efforts to maintain intellectual control tend to push complexity down. In my experience, many teams let their intellectual control atrophy and then compensate with more testing. This approach works for a while, but without intellectual control to keep complexity down, progress becomes slower and more difficult. Once lost, intellectual control is expensive to recover, so the teams find themselves in a local maximum they cannot escape.

中文翻译：

---

测试使我们对失去智力控制感到麻木

似乎今天，通过我们所有的测试，我们允许代码以过去没有自动化回归测试的方式变得毛茸茸和复杂，这是我们永远无法容忍的。我们被迫保持代码简单，因为如果我们不这样做，特殊情况的复杂性将无法适应我们的头脑。这使我想到了以下想法，我将在本文的其余部分深入探讨：软件团队需要在来自推理的智力控制和来自测试的统计控制之间取得健康的平衡。复杂性是推理的敌人；保持智力控制的努力往往会降低复杂性。根据我的经验，许多团队让他们的智力控制萎缩，然后通过更多的测试来弥补。这种方法有一段时间有效，但没有智力控制来降低复杂性，进展变得更慢和更困难。一旦丢失，恢复智力控制的成本很高，因此团队发现自己处于局部最大值，无法逃脱。