Live data from Hacker News

10x Engineer

medium.com

11–20 of 186 posts

Re: 10x Engineer

#11
I spent Saturday digging out a basement with my son. The kid was a machine—for sure he did an order of magnitude more than I did. There's your 10x right there. If you can see it with picks, shovels, and a wheelbarrow, it's hardly implausible that you would see it in software.

The research literature on programming productivity sucks, but not because 10x is a myth. It sucks because we have no reliable way of measuring these things.

Re: 10x Engineer

#13
post #3

If I'm being generous, I'm a slightly above average engineer. Spot me 10X and I'll outperform any engineer on the planet. Do I believe in the 2X engineer? Definitely. 3X? Sure. 5X? Possibly, if their name is Ritchie or Torvalds or the like. But 10X? What I do in a week, they'd only get 4 hours. What I do in a year, they'd get 5 weeks. Doesn't exist.

OK, so there is an 5x engineer relative to you, and you're above average. And on the other side of the bell curve, there is an 0.2x engineer. This makes relative difference of 25x from the worst to the best - bang - QED.

Re: 10x Engineer

#14
post #3

If I'm being generous, I'm a slightly above average engineer. Spot me 10X and I'll outperform any engineer on the planet. Do I believe in the 2X engineer? Definitely. 3X? Sure. 5X? Possibly, if their name is Ritchie or Torvalds or the like. But 10X? What I do in a week, they'd only get 4 hours. What I do in a year, they'd get 5 weeks. Doesn't exist.

How are you measuring performance?

The 10x concept contains not only the work but the decisions. Not just how to build something, but what to build.

For example, people other than Linus Torvalds can code at the level needed to write and maintain git--as evidenced by the fact that other people do that now; he has handed the project off.

But the creation of git included the conception of git--the many decisions about what he would build, and why it should be that way. Those decisions, coupled with solid coding, have resulted in a massive productivity multiplier for many thousands of people.

Re: 10x Engineer

#15
What's the point of being a 10X engineer somewhere, if you don't own the IP? It sounds like a way to make someone else rich off your hard work.

Re: 10x Engineer

#16
post #5
post #3

If I'm being generous, I'm a slightly above average engineer. Spot me 10X and I'll outperform any engineer on the planet. Do I believe in the 2X engineer? Definitely. 3X? Sure. 5X? Possibly, if their name is Ritchie or Torvalds or the like. But 10X? What I do in a week, they'd only get 4 hours. What I do in a year, they'd get 5 weeks. Doesn't exist.

It's possible they can do things you can't do at all or can't do in a reasonable amount of time so 10x is certainly possible simply because they could have far superior knowledge.

I think the danger of the myth arrives from the idea that one can label some engineers as consistently 10X better than their peers, regardless of the actual tasks, personal lives, health, etc.

Re: 10x Engineer

#17

What are the units we are talking about here? Is productivity measured in hours and if so hours of what?

One way to measure productivity is how fast you can create what the marketing people want. I can't think of any way better than that, and it's really ambiguous.

Re: 10x Engineer

#18

What are the units we are talking about here? Is productivity measured in hours and if so hours of what?

I believe that was one of the points of the article. "10x Engineer" is being thrown around as another euphemism for "Rockstar" or "Ninja" without any true meaning.

Re: 10x Engineer

#19
post #7
post #3

If I'm being generous, I'm a slightly above average engineer. Spot me 10X and I'll outperform any engineer on the planet. Do I believe in the 2X engineer? Definitely. 3X? Sure. 5X? Possibly, if their name is Ritchie or Torvalds or the like. But 10X? What I do in a week, they'd only get 4 hours. What I do in a year, they'd get 5 weeks. Doesn't exist.

The 10x "mythology" doesn't mean 10x productive as an above-average engineer. It means 10x productive as the least-productive. So think of somebody who would consider you a 3x. Now the engineer who is 3x relative to you is just about 10x to them. Now consider the developers with net-zero or net-negative productivity. The 10x rule wildly understates how much more valuable a good engineer is relative to them.

Then the mythology is worthless. The focus should then be on eliminating bad engineers, not to go chasing after unicorns. Or even more importantly, figure out why some "10X" become "0X", or vice versa.
Post reply on HN