职业与工作方法benjiweber.co.uk
为什么我努力做一名 0.1x 工程师
Why I Strive to be a 0.1x Engineer
2016 — 2022，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
作者以'0.1x 工程师'自嘲，主张工程师的价值不在于写了多少代码，而在于尽量少写代码、少做不必要的工作：优先复用现成方案、删减冗余、考虑维护的人力成本。文章以半玩笑的方式回应了'10x 工程师'这个流行说法。
为什么经久不衰：它把'少即是多'的工程智慧讲得通俗有力，在代码膨胀和 AI 生成代码泛滥的今天，'最好的代码是不写的代码'这一原则依然值得反复提醒。
HN 评论精选
用 Clyde/Bob/Alice 的例子说明：选最省力的方案解决问题才是真正的高效，代码量不等于生产力。
我职业生涯中一直把这种'不做事'的技能和'10x 开发者'混为一谈。比如客户要一个 CMS：Clyde 凭深厚功底花几个月手写几十万行代码，架构精良；Bob 用现成框架和 ORM 花几周写几千行，更贴合客户需求；Alice 发现客户用 Wordpress 加点调整就够了，搭个托管博客完事，她有更好的事要做。Alice 做得最少但效率不低——你是在解决问题，产出多并不让你从 1x 变成 30x。
cpdean查看英文原文
Throughout my career I've definitely been lumping the skills described in this article about not doing work in with the whole "10x developer" catch phrase. Like: Customer needs a CMS. Clyde looks at the requirements for the CMS. He sets off to write hundreds of thousands of lines of code by himself, complete with CI, continuous deployment, tests and documentation because he is a very good developer. Through the course of the project he leverages his years of experience and background in CS and engineering to make a well-factored body of software that will be maintainable for years. He did this in only a couple months. Bob looks at the requirements for the CMS. He thinks "I know, I will use a good application framework and an ORM". Bob writes a couple thousand lines of code with all the tests and stuff that Clyde had. Bob's tests and app code, however, are more focused on the customer's needs, making in maintainable for anyone who can read the documentation of the software he's chosen to use. It takes him a couple weeks. Alice looks at the requirements for the CMS. She realizes the customer will do just fine with Wordpress with a couple of tweaks. She sets up a hosted blog so nobody has to actually maintain it. She has better shit to do with her time. Alice did the least work but that doesn't make her less productive. You're solving problems. If you do work to solve those problems, fine, but having more "output" doesn't make you go from a 1x to a 30x engineer.
引用 Atwood 等人的名言佐证'少写代码'是业界共识。
再补充两句关于这个话题的名言。Jeff Atwood：'最好的代码就是没有代码。你写下的每一行都要被调试、阅读、理解、维护，所以写新代码应该是不得已而为之。' Robert Galanakis：'跑得最快的代码是不运行的代码，最好维护的代码是从未写过的代码。'
karlb查看英文原文
Two more quotes about this subject: Jeff Atwood: “the best code is no code at all. Every new line of code you willingly bring into the world is code that has to be debugged, code that has to be read and understood, code that has to be supported. Every time you write new code, you should do so reluctantly, under duress, because you completely exhausted all your other options.” Robert Galanakis: “The fastest code is the code which does not run. The code easiest to maintain is the code that was never written.”
批评文章用流行语做标题党，导致内容臃肿，与主旨自相矛盾。
'少即是多'这个核心观点很好，却被'10x 工程师'之类的流行语包装得晦涩难懂。标题党带来了流量，但代价是作者花了至少 30% 的篇幅去解释这些流行语，没什么实质内容。有点讽刺：一篇主要讲避免生产环境冗余的文章，自身就包含不少冗余。
johnloeber查看英文原文
The fundamental point ("less is more") is a good point that is needlessly obscured by a layer of buzzword-talk ("10x engineer", etc.). Using the buzzword-talk makes for a nice clickbaity headline, but as a consequence, the author spends at least 30% of the article addressing and explaining things related to the buzzword of choice. Such discussion is of little substance. Ultimately, the article can be distilled to a few central tenets (e.g. "don't build anything unnecessary -- think about the human costs of maintenance"). I consider this somewhat ironic: the article, which is chiefly about avoiding cruft in production, contains a fair amount of cruft.
指出文章本质是对'10x 工程师'网络梗的调侃式回应，读者不应过度当真。
那些说作者描述的其实就是 10x 工程师的人，没注意到他批评的是'10x 工程师'这个梗，而不是真正高效 10 倍的工程师。这更像是一篇回应玩笑梗的半玩笑文章，顺便带出一些好观点，而不是一篇严肃批评真正高效工程师的文章。
satvikpendem查看英文原文
Those here talking about what the author is saying is actually a 10x engineer are missing that he's criticizing the meme of a 10x engineer [0] over an actually 10x more productive engineer. In a way, it's more of a joke article responding to a joke meme that has some good points over actually being a fully serious article criticizing actual 10x more productive engineers. [0] https://knowyourmeme.com/memes/10x-engineer
历次讨论
同类还值得读
用十年时间自学编程（1998）
Teach Yourself Programming in Ten Years (1998)
Peter Norvig 1998 年的经典文章，回应“21天/24小时学会编程”一类速成书，主张真正精通编程需要约十年持续、有意识的练习。
职业与工作方法上首页 11 次 · 2007–2025norvig.com编辑精选如何成为一名程序员：简短、全面而个人的总结
How to be a Programmer: A Short, Comprehensive, and Personal Summary
一篇广为流传的程序员成长指南，作者以个人经验系统总结了成为优秀程序员所需的各项技能——从调试、测试、沟通到团队协作与身心健康。
职业与工作方法上首页 6 次 · 2008–2015samizdat.mines.edu编辑精选不要自称程序员
Don't Call Yourself a Programmer
经典职业建议文章劝软件工程师不要把自己局限在“程序员”这个标签上，而要从公司业务角度说明自己创造的价值；文中讨论了成本中心与利润中心、头衔、求职与职业选择，也顺带批评了学术界的价…
职业与工作方法上首页 5 次 · 2011–2021kalzumeus.com编辑精选创作者的日程与经理的日程
Maker's Schedule, Manager's Schedule (2009)
Paul Graham 在这篇文章里把时间表分成两类：管理者的日程以小时为单位，会议可以填满一天；创作者（程序员、写作者等）的日程则以半天为单位，需要长时间不被打断的连续块。
职业与工作方法上首页 5 次 · 2009–2021paulgraham.com编辑精选为什么程序员的薪酬不与生产力成正比
Why programmers are not paid in proportion to their productivity
讨论为什么程序员的薪酬往往不随其生产力成比例增长：生产力难以客观量化，薪酬更多受组织预算、岗位定价和个人议价能力影响。
职业与工作方法上首页 5 次 · 2009–2022johndcook.com