百倍开发者
100x Developers

原始链接: https://jcarreras.es/posts/100x-developers/

作者认为"100倍开发者"的说法被夸大且不切实际,尤其在企业环境中。虽然AI可以在特定狭窄场景下产生巨大倍率——如新手、微小任务或衡量任务影响——但大多数此类说法都来自没有代码债务、代码审查或利益相关者的单人、低摩擦项目。真正的企业工作涉及协作、遗留代码和限制收益的人类流程。在团队中,2倍的提升已经很出色;10倍是罕见的,100倍基本上不可能。作者安慰开发者不必因未能达到这些虚高的数字而焦虑,并专注于现实、可持续的进步。

Hacker News 的评论者讨论关于“100 倍开发者”的说法,尤其是在 AI 的背景下。他们指出,最初的 10 倍概念比较的是特定任务中表现最好与最差的开发者,而现代用法很模糊:是一个开发者与一个团队相比,还是与普通开发者相比。有人举出小型精锐团队胜过大型组织的例子,如 WhatsApp 与 Facebook Messenger。其他人对 AI 生产力的说法持怀疑态度,认为这些说法依赖拉取请求等输入指标,而非业务成果,且一些报告的收益被夸大。评论者还争论低技能开发者是否从 AI 中受益更多、按地区调整的薪酬是否重要,以及极端倍数是否合理。总体而言,该帖混杂了轶事、玩笑和对衡量开发者生产力的疑虑。
相关文章

原文

Think about it. 10x of something is a lot.

  • 10x a salary of $70.000/year (~avg salary in USA) is 700k€/year. Imagine the lifestyle change.
  • Lifting 10x my maximum PR on dead-lift goes from 160kg to 1.6T.
  • A means of transportation 10x faster is arriving in 9 minute what it took 1.5h
  • Avg. vertical jump for an male adult is 45cm. 4.5m if you 10x it.

We referenced the mythical 10x developer casually in the dev world. Now that we have AI, we’re mentioning the existance of 100x developers!

It bothers me. Not because it might be true or false in particular instances, but because the number just scapes me. 100x. It’s a lot if talking about productivity.

Lets put this number in perspective. In 3 days, at 100x and you achieve the work of 300 working days. There are 260 working days in a year. That sounds unrealistic.

Steelmanning the “100x case”

Under some circumstances, I think it’s possible to have such a big multiplier:

Newbies. You know absolutely nothing about programming. Doing a full website, including frontend, backend, DB access, prod setup… that’s a lot of work for someone who’s knows nothing. You’ll be blazing fast using AI compared to the time it would take without.

Super small or specific task. Tasks so small that AI can do them in 10 minutes, were you would take almost 3 hours. Examples:

  1. AI troubleshooting a production problem involving many services, with access to source code, logs, traces, etc…
  2. Classifying and prioritising tickets/issues on a given criteria
  3. Finding the root-case of a flaky CI tests

Measuring task impact, instead of developer productivity. “In 10 minutes of vibe coding I saved 10 minutes a day to every engineer in the organisation”. You’re measuring the impact of the completed task. But if the task would have been done manually taking 1 hour, the impact would have been big as well, right?

10x/100x projects

So, 10x of what? 100x measured how?

What’s the metric being measured, here? It can be: Productivity. Lines of code. MRs. Reviews. Deployments. Impact (how you measure it?), features shipped, business KPIs’ growth, …

I bet that most developers claiming to be 10x because of AI are working on a personal projects or uni-personal companies.

I bet they are measuring lines of code, MRs or deployments.

I bet are projects without other people involved. Without a PM, or a wide-company vision. Without needing to align with older codebase. With a single (small) codebase. No code-debt. Without required MR reviews. Most likely very few (if any) clients.

Remove all human interaction and work alone and I fully believe that you can be a 10x developer.

A 100x developer it’s a stretch. I think it’s still too much of an exaggeration.

But those are great news! I feel 5x to 10x when working on personal projects! I’m having loads of fun. But this doesn’t translate to my experience when working at a company.

What about corporate?

If you’re in a Product team, and AI is improving your feature lifecycle by 2x? It’s already great.

I think 10x is crazy, altho in some cases it might be attainable. 100x is just a figure of speech. It’s just not possible.

Are you feeling down because AI is everywhere around you and you’re supposed to be working at 10x, 50x or 100x? Is this causing you anxiety? Please relax and take it easy. If you’re doing 2x as a team, it’s great already!

联系我们 contact @ memedata.com