Stop Chasing 10x Programmers: Build Systems That Work Even When Your Best Engineer Leaves / 别再追捧“超级程序员”了：打造一套哪怕核心成员离职也能正常运转的团队体系
I recently came across a thought-provoking piece that pushed back hard on the cult of the \"10x engineer\" that so many tech teams obsess over. The core argument is surprisingly simple: enterprise software development is first and foremost a problem of managing complexity, not a showcase of individual skill. If your team can only hit deadlines, avoid bugs, or scale features because one or two star employees are carrying the load, you don't have a successful team — you have a ticking time bomb.
我们应该都见过网上那种“超级工人”的视频吧：流水线上的工人手速快到像开了倍速，或是建筑工人能凭经验徒手搞定极其复杂的操作，看得人叹为观止。但这类场景放到企业项目里其实是巨大的隐患：你可以赌这个“超级员工”永远不跳槽、永远不生病、永远不出状况吗？只要这个人一走，之前靠他撑起来的效率、质量、进度就会全面崩盘，本质上这不是他厉害，而是你整个工作流程本身就不合格。
The author makes a great point that a good system isn't just a list of rigid rules for people to follow — it's built on the realistic assumption that all humans make mistakes, get distracted, and have off days. For example, instead of just telling your team never to push directly to the master branch, you can configure your repository to automatically block direct pushes entirely, so even a sleepy engineer making a mistake at 10 PM can't accidentally break production. That's the magic of systems: they don't require perfection from people, they guard against imperfection automatically.
很多团队会抵触搞流程、搞规则，觉得这是不信任员工、束缚创造力，但其实规则越完善，反而越能解放普通开发者的精力。就像我们写代码修复一个bug之后，不能只改完代码就完事，还要补上对应的单元测试，防止以后其他人改代码的时候再踩同一个坑。团队流程也是一样的：每遇到一个共性问题，就把解决方案固化成流程、写成文档、做成自动化工具，最后哪怕整个团队的人都换了一遍，新人只要跟着规则走，也能交出合格的成果。
Of course, building these systems will often get pushback from people who benefit from being the irreplaceable "expert" on a team. The author shared a story from their own React project where they wanted to add a simple rule to memoize all values returned from hooks to fix recurring re-render performance issues, but one engineer fought the change tooth and nail, citing "premature optimization" and "React docs don't recommend it". In reality, that rule would have eliminated an entire category of repetitive work, taking away the opportunity for that engineer to spend hours fixing the same memoization bugs over and over to look like a hero.
说到底，好的团队不是要磨灭个人的能力，而是要把个人的优秀沉淀成整个团队的财富。我们当然可以鼓励员工提升个人效率，但绝对不能把团队的命运赌在某几个人的个人能力上。比起费尽心力挖来几个“超级程序员”，花时间打磨一套能让普通人也能稳定输出高质量成果的体系，才是真正能让项目走得长远的事。毕竟没有谁是不可替代的，真正不可替代的，是一套成熟、自洽、能自我迭代的工作系统。
