I don't think this is really in good faith, what is meant by 10x programmers is exactly that they are 10x more productive in grinding jira tickets, not that some people know more and are wokring on harder problems, etc.
10x programmers aren't going to be good at grinding tickets.
they'll procrastinate on them because they are boring and tedious and will go work a massive project instead because it's fun to them.
they'll finish that massive project in the time everyone is fiddling their thumbs with the stupid back and forth of the meetings and whatnot of those "tasks".
if you are lucky to get one of us, let us run free, we'll make you some really cool shit without any input.
if you stifle us and try to fit us in a box, we won't make shit. we'll eventually get bored, pissed off, and leave.
oh and don't touch our code, it's beautiful, and it's the only way it'll work, trust us! ideas welcome, code not!
we don't like teams. one person, one thought, one architect, one vision, one program.
source: am one, believe me or not idc, i prefer being mythical.
Anyone would work faster and better alone, it just doesn't really scale. Building something yourself is much easier than working in a team, the bigger the teams the harder it is.
i agree, except for the scaling, a 10x can make an entire project it takes 100s of engineers for, and they'll do it in magnitudes less code.
but that long topic aside... i was just pointing out the ideal environment for "10x programmers".
you put a 10x on a team and treat them the same, they become a 1x (or worse because they are bored and procrastinate), the others will drag them down to their level.
to make teams work, let the 10x design and develop the initial system solely. then the 1x work in a scoped domain (using a plugin/extension system etc) within the 10x's vision
well, if it's a short term use and throw kind of project/tool then sure I can go with 1 "10X programmer", but if I were a stakeholder in a long term project I wouldn't put all my eggs in a one person team.
Reminds me of a software team having one surgeon and the others are support staff--in no way denigrating, but equally essential with their skillsets, to execute on the (skunkworks?) project.
I think it’s means “there are coders out there who are consistently 10x more impactful than the average coder,” and this could be the result of simply speed or through other methods — finding better solutions etc.
Exactly this. I’ve seen architectural decisions that over time lead to exponential work to implement new features. An architectural fix can lead to a big-O difference in productivity, not just 10x (a constant factor).