10 ms·
This is a very insightful list. But there is one thing I'd quibble with: while it's inherently a super-subjective metric, I would say that 10x programmers do ex
by pjc50 5y ago
This is a very insightful list. But there is one thing I'd quibble with: while it's inherently a super-subjective metric, I would say that 10x programmers do exist. Both in the "can support a company by themselves" sense and the "mad lone genius" sense. Not all the 10x programmers are good at working with other people or on other people's ideas.
0.1x programmers are often lost or afraid, although they may just be unimaginative. The real risk of fear is introducing 0.1x processes. People are often willing to sacrifice any amount of development velocity to avoid being seen to make mistakes.
Sometimes this makes sense, sometimes it doesn't. Arguably the reason for the success of SpaceX is that they were willing to fly, crashland, and improve a dozen rockets in the time that a conventional company would spend agonizing over whether to launch at all. On the other hand, nobody wants to be on the same roads as the "move fast and break things" self-driving car.
- Nursie 5y ago-1x programmers also exist, in a variety of guises. From the dev with long cv of projects he’s contributed nothing to and been sidelined from, but who manages to keep getting hired because of his cv, to the dev who crowbars in new tech where it’s not needed and causes a ton of problems.
- deleted 5y ago[deleted]
- lucumo 5y agoPresumably a 1x programmer is an average programmer. The type who does his job acceptably. He doesn't create huge problems, nor solve them. He is a fine team player and team member, but not a leader. Nobody despairs when he leaves, and he will be forgotten after a few months. Basically, the majority of programmers.
- heipei 5y agoThis was about minus 1x, so having a negative impact. And yes, these do exist.
- mushishi 5y agoNow that I think about it, the worst code seem to lead to situations where the top developers can really show their value. I mean if the code base is quite good and is kept that way, then a normal developer can deal with it quite well. But if you get a legacy mess, then the hard-core developer can make really drastic changes that have enormous value to the maintainability, future development and bug-wise. If a normal developer tries to tackle that mess, it's easy to get into trouble and drown in the sea of opportunities and not see the big picture and take a proper road plan to improve things. So in a way -1 developers enable the top developers to show the gap between them and the normal devs.
- Koshkin 5y agoThis could be managers who deem themselves programmers or software architects. (Often they would use their authority to promote their ideas and effectively shut everyone else up.)
- mettamage 5y agoI've also met one 10x programmer in my life. A lot comes down to being able to reason fast, architect well, and write code on the fly without resorting much to: * Documentation * The debugger / print() Becoming a 10x developer means that you have a set of skills that work well together in an end to end process from going to initial requirements to fully fledged architecture and/or code.
- Aeolun 5y agoBeing a 10x developer is a factor of experience. You don’t need to debug the issue if you can already reason through to where it must be.
- Jensson 5y agoYes, but some people generalize their experiences much much better and therefore can master domains and adjacent things to a degree others will never reach.
- louthy 5y agoI think most people who have worked with me would consider me a 10x developer, I am capable of writing something in hours that would take others weeks (not in a half-arsed way, but taking all of the complexities of the domain into account). And I think that's what most people think a 10x'er is: that they can just do stuff quicker. That's not what I think 10x'er is though. I think a 10x'er is someone who enables the 'average' developer to become a 2x, 3x, 4x developer. This can be through writing some core tech, a library used by all, or through mentoring and guidance. The 10x'er can then become a 100x or even 1000x developer. The 10x dev is the person who picks up the really difficult or ugly stuff and says: "Hold my beer, I'll get that done" - motivating the team and helping them to keep velocity. They lead by example and explain to the team why they've taken the approach they have. Sometimes people use the term Rockstar to define a 10x developer. I think that's a loaded term that comes with an 'arrogance' tag. The true 10x developers shouldn't be arrogant (beyond the base level arrogance everyone of ability has), they can and should be the glue that holds a team together and helps everyone achieve more.
- davedx 5y ago> People are often willing to sacrifice any amount of development velocity to avoid being seen to make mistakes. I'm living this at the moment and it's driving me crazy.
- grey-area 5y agoPeople are often willing to sacrifice any amount of development velocity to avoid being seen to make mistakes. IMO that attitude never makes sense - it can make sense to avoid certain mistakes at all costs (self-driving car), but it never makes sense to try to avoid blame for them (company refuses to admit their car isn't good enough). This is a problem of culture, not individuals. Does the culture at a company openly admit mistakes, try to learn from them, and put systemic fixes in place to address them, or do they punish people for mistakes? If the latter, you end up with nobody admitting to mistakes and a terrible culture, it's not about the people, it's about the situation you have put them in and the incentives given to them.
- pjc50 5y ago> it can make sense to avoid certain mistakes at all costs (self-driving car), but it never makes sense to try to avoid blame for them Eh? As you say, it's a culture thing, and the culture of a lot of humans is that the mistake only matters if you take blame for it. Plenty of people and organisations put more effort into avoiding blame for things than the thing itself. Blame-free culture is great, but it has to be actively maintained.
- grey-area 5y agoPlenty of people and organisations put more effort into avoiding blame for things than the thing itself. Blame is pointless (particularly directed at humans), learning from mistakes is invaluable. What I'm saying is it is a terrible mistake to put more effort into avoiding blame than avoiding mistakes. Blame-free culture is great, but it has to be actively maintained. I agree.
- isolli 5y agoNo, it's also a matter of personality. One manager used to urge me to do things in half the time at 90% of quality, and stop chasing the remaining 10% at such high opportunity cost. To this day, I try, but it's hard to overcome a natural, obsessive tendency.
- jasode 5y ago>, I would say that 10x programmers do exist. Yes but I think the underlying issue is that some people really Really don't like to acknowledge (or are unaware) there's a small set of elite programmers that can do things average coders can't. But any label we use to describe them (i.e. "10x", "rockstar", "ninja", etc) will be psychologically distasteful. I previously commented about that effect: - https://news.ycombinator.com/item?id=13753178 https://news.ycombinator.com/item?id=13753178 - https://news.ycombinator.com/item?id=24753594 https://news.ycombinator.com/item?id=24753594 To see that hidden psychology driving the narrative... look at how the author constructed his comparison with extra qualifiers of "competent" & "similarly experienced" : ">The idea that someone can produce in 1 day what another competent, hard working, similarly experienced programmer can produce in 2 weeks is silly." In other words, if we artificially construct the comparison by a priori assuming both programmers are equal, then the 10x difference is a myth. Well yes, that's tautology. If you invent a sentence to "prove" a point, you can set any conditions in the artificial universe in your favor that seems to support it. However in the real world, the stack of resumes will have a candidates with wildly different skill levels. Some struggle with Fizz Buzz. Some can write a 3d game from scratch. But it's impossible to create a label to describe that wide gap which also doesn't invite bikeshedding on that label. EDIT reply to: >"Why can't we call them master programmers?" Because we'd still have endless bikeshedding of the label "master" as in "Master programmers are a myth..."
- willcipriano 5y agoWe don't call Vermeer a 10x painter, Beethoven a 10x composer, nor Shakespeare a 10x author. It would be silly to call Turing a 10x computer scientist, or rockstar and ninja would be insulting. Vermeer, Beethoven and Shakespeare are masters of their crafts. The same word we use for skilled tradesmen. Why can't we call them master programmers?
- bilger321 5y agoI think part of the reasoning is in the trades there's the presumption that to be a master you must also be old (with exceptions, Da Vinci was active when he was still younger, 20). In the programming industry, there's likely a bias more toward younger people, and hiring offices ask for the world. They'd like a whole staff of masters and rockstars. Though that doesn't preclude "older" people from being known as masters either. Take John Carmack or Jonathan Blow, for example.
- e1g 5y agoMy go-to examples of 10x developers are benevolent dictators like antirez (of Redis), evanw (of esbuild + Figma CTO), youyuxi (of Vue), Carmack, etc. Both qualitatively and quantitatively, their output is at least 10x of a typical developer at a typical company, not even counting everything these people do besides writing code. Many more are not famous but are in the same league of impact/productivity - I'm genuinely puzzled how someone can say such people do not exist.
- ignoramous 5y agoYou mix popularity with 10x. Not all 10x programmers are popular. I believe 10xers exist within a business or technical context. This isn't limited to the field of computer science, but even traditional engineering (Edison) and sciences (Newton) have plenty 10x examples.
- e1g 5y agoI'm not mixing - as I wrote, many more are not famous, but their impact is similar. When discussing abstract concepts, it helps to have concrete examples of that phenomena. Using "famous" people is a shortcut to define a shared definition for what "10x" might look like. And yes, there are "10x" teachers, investors, lawyers, storytellers, sales folks, etc. Similarly, the distribution of talent that helps with "software development" might have a very long tail, leading to extraordinary performance versus the median.
- texasbigdata 5y agoIF 10x exist, some will be popular and most won’t. Obviously he won’t know the obscure ones or pick examples you can’t relate to. So while he didn’t prove his point perhaps, perhaps you didn’t disprove his either. :)
- randomsearch 5y agoTo pose it another way: for general software Dev (not some niche use case that only one guy understands), let’s say building websites in Vue or React, the idea of a 10x developer is that they can work in January and another, average, programmer can then spend February, March, April, May, June, July, August, and Sept… and the average guy won’t get more done? Or they come in only every other Monday and contribute as much as a median Dev working full time? It just doesn’t seem reasonable at all, at least if we read it literally. I have worked with and met great, outstanding, developers who are much better than me. Some of them famous. None of them are anything close to 10x as productive, and I’m not particularly great. They’re much smarter than me, for sure, but they’re not 10x as productive.
- itsibitzi 5y agoSaying 10x programmers are a myth because it's crazy that someone could do in 1 day what another could do in 1 week makes the assumption that both programmers in the example have the same amount of context, background understanding, and experience. The benefit of talented engineers comes from the fact that they avoid costly pitfalls - not that they pump out more code per hour worked. I feel this "10x programmers are a myth" attitude comes from a good place of wanting to promote harmonious working and skill-up junior engineers, but it seems so totally detached from reality. I'm not sure the "benefit" of propagandizing against talented assholes is worth the cost of demotivating people who might be inspired that they could become a 10x engineer.
- WhompingWindows 5y ago1 day vs 1 week: wouldn't that make them a 5X engineer? That's half of the advertised 10X...
- dijit 5y agoI always read it as a direct comparison though. It doesn’t matter if I have better experience or I can contextualise intent better; the phrase “10x” means it would take a team of 10 to do it, in the time, scope, budget (whatever). But there are major reasons this could be the case, if I’m on my own and I know the direction then I don’t have to quibble about what framework to use, how to name my variables, what I consider “proof of concept quality”. You just get your head down and do it with the entire scope and progress in your head at once. No infighting about semantics, no deeply technical progress reports or trying to subdivide tasks which are not inherently subdividable. More people is more communication and it’s quadratic.
- obedm 5y agoThe author exactly says this "two engineers with the same experience". I'm sure there are engineers that can create an architecture 10x better than mine. But show me someone that can create UI 10x faster and I'll admit they're a God. Some things can't be 10xed after some point. It just takes work. Some things can be 10xed and some just can't. I find it silly to think someone can be overall 10xer at everything.
- grecy 5y agoI once worked on a team that in hindsight had two 10x developers in a team of only 12. They were vastly different, and the difference to me is extremely interesting. The first one was not a bad person by any means, but had no social skills, no ability to communicate and often just forged ahead building great stuff on his own. Entire areas of the software were entirely conceived and created by him, and it was difficult to even grasp what he was doing while pair programming with him. In a day he would write more tests and get more coverage than the rest of us would create in a week. The second one had come from a FAANG-ish place where he was extremely successful, but didn't want the money or stress. He was extremely kind, considerate and great at communicating. Pair programming with him was a joy and he helped everyone else on the team grow. I'm confident he could have created entire regions of the software on his own, but he knew that wasn't the right thing to do. He would often ask questions until someone else on the team could solve a problem, even though I'm sure he knew how to solve it easily himself.
- xwolfi 5y agoYeah the first one is a risk. I've met one whom I had to take over the code of when he left and psh, I wished he was a dumbass instead. He could produce shitloads (but would never test, interestingly), do stuff I honestly can't do, but do you really need to bitshift instead of doing a modulo to save 1 CPU instruction ? The amount of obscure waste of programming complexity made us actually just abandon the thing he spent years on to just not do it. And everything works fine and we still make money and we're just probably a little bit less clever about how we do it. We also have a lot more time to listen to users and solve their problems, rather than gloat on our genius and solve our own created problems :D Your second example is inspiring and I hope to meet one to learn from too !
- mosburger 5y agoI like to say that I am a 10x developer 10% of the time. My work tends to be very "bursty" followed by long bouts of low productivity. It probably has more to do with my mental health than anything else. :/
- vicda 5y agoSounds like ADHD hyperfocus.
- sumtechguy 5y agoThere can be that. But also some managers do not like you wander off task. So stick in your lane stick to your tasks... So eventually after years of that you just do only what is needed and skip anything else. After a few of those 'that is very nice but...' conversations you just say screw it and coast. Every once and awhile I get a burst where I can propel my group forward. But then usually I feel like I am bolder chained to them and dragging them down. More than likely I am just average and doing OK.
- bkromhout 5y agoWas just coming here to say, this is my exact situation
- dgb23 5y agoI have the same problem. But the more I tackle it in reasonable ways, the better it gets. Here's some pointers that work for me: - enough sleep, rather get in bed early than late as the quality of the sleep depends on natural rhythms - engage with people that are affected by my work - this is important for motivation and to keep track of what actually matters - operationalize everything, say out loud what to do next - being honest when I have bad focus, talk about it - trust my instinct and do the right thing, if I don't I quickly lose focus and motivation, if opinions don't align learn why
- pjc50 5y agoMy personal joke about this is "I used to be a 10x developer but then I took an arrow to the knee". Many, many years ago a colleague wrote about the experience of being bipolar and choosing to stop taking the lithium for a temporary productivity boost and subsequent crash.
- majgr 5y agoI like FactoryFactory devs, they are even worse than 0.1x. After some time every other team member who touches their code becomes 0.5x.
- lukaslalinsky 5y agoAnd then you encounter the 10x programmer, who is not afraid to throw the bullshit code away and write it in a way that is easy to manage for other devs. I'd say this is really a more realistic example of a 10x programmer. Most programmers are just afraid of asking the "why" question and the actually acting if there is no good answer.
- kirubakaran 5y agoI'm not claiming to be a 10x developer or anything like that, but I have a related story to share: Once I had to tweak a 7000 line signal generator (ie spits out wav files) written in Java. It had a mind boggling structure, and I'm sure whoever wrote it was a mad genius of some kind. I rewrote it in less than 100 lines of Python, where each signal primitive was basically a few lines of code max, which you can functionally combine. Since this new program was not even 100 lines long, we were able to do a LOT more with it, and in a super flexible manner. It's one of my happiest accomplishments.
- lazide 5y agoAlso, sometimes it isn’t someone ‘moving fast and breaking things’ - sometimes everyone else gets paralyzed with indecision and can’t even get started. Someone who can sit down and start coding in an ambiguous environment, period, can easily make 10x more value themselves, and allow others to go from .1x to 1-5x merely by being able to pick somewhere to start and just doing it, which allows everyone else to break their own ‘freeze’ and start engaging as now there is something concrete that breaks the locked up state they were in. I’ve done it a few times, and seen others do it to. It’s magic going from ‘everyone rehashing things on a whiteboard for the 10th time’ to ‘everyone working on the next iteration’
- pjc50 5y agoThe "MVP" or "strawman" is incredibly valuable; people can't tell a blank sheet of paper what they want, but if you show them a thing they'll tell you what's wrong with it. I've noticed myself that I can happily write detailed comments on HN or StackOverflow but have no inclination for blog posts, for that kind of self-content-marketing that seems to be popular these days.
- bigbizisverywyz 5y ago>sometimes everyone else gets paralyzed with indecision and can’t even get started. I once worked on a project where exactly that happened, and I view it as one of my biggest failures of my career. I often wonder why I didn't just sit down one day and type int main( ... and just get on with it. In the end the project got canned and both contractors terminated early, so I made sure that never happened again.
- AlexCoventry 5y agoI think he's beating up a straw man, here. > The idea that someone can produce in 1 day what another competent, hard working, similarly experienced programmer can produce in 2 weeks is silly. Over such short time scales, maybe, but the idea that someone could contribute in 1 year what another programmer wouldn't accomplish in 10 years is highly plausible, to me.
- fouric 5y ago> while it's inherently a super-subjective metric, I would say that 10x programmers do exist Even worse than super-subjective, it seems like people don't agree on the definition of "10x programmer". Is that 10x value (code * code quality) produced per unit of work-time? Per brain cycle? Are you controlling for programmer experience, or domain knowledge, as [1] pointed out? Do you actually mean 10x, or is that a stand-in for "significantly more productive" with an unknown value? Do you include collaborative skills and working with a team, or even entirely base your definition off of that? I'm both curious as to the exact definition you have in mind, and also trying to point out the more general issue so that others arguing past each other can realize that they have two different ideas in mind. [1] https://news.ycombinator.com/item?id=28797923 https://news.ycombinator.com/item?id=28797923
- pjc50 5y agoFor me, it's definitely "a stand-in for "significantly more productive" with an unknown value". Neither the input nor the output can be properly quantified, and we don't really know the full set of variables to control for, and it inevitably runs into serious questions of inequality, SES, and background that are likely to make people even more cross. I see it as more of a compliment. Nobody should be seriously and unironically calling themselves a 10x programmer, it should be bestowed by other people.
- Jensson 5y agoHave a 1 year project. One side is a team of 10 developers with 5 years of experience in the field. Other side is 1 developer with 5 years of experience in the field. Do you think it is unreasonable that there is any developer that could beat the team in that situation? The quality expectations for both are the same, so no shortcuts. I don't find that unreasonable at all, most teams are very unproductive. So what I'd call it is "A 10x developer is a developer who can outperform a typical team of 10 developers".
- superpope99 5y agoMaybe 0.4x and 3x programmers exist, and so when you introduce a little noise it's easy to perceive as a 10x difference at certain points in time.