5 ms·
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 som
by nathias 4y ago
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.
- philipswood 4y agoI think this touches the base of the disagreement about their existence: the unspoken definition being used. When I hear 10x programmer I definitely don't think "that they are 10x more productive in grinding jira tickets." I think there are programmers who can build something that would take ten or more other developers to replicate. And that's "easy" since some people can win by choosing the right game to compete in.
- onos 4y agoI 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.
- nathias 4y agothe most impactful are the architects, their bad decisions echo through eternity of code spaghetti
- BenFrantzDale 4y agoExactly 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).
- MrOwnPut 4y ago10x 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.
- robofanatic 4y ago> we don't like teams. one person, one thought, one architect, one vision, one program. Hope this is satire. Otherwise its a horrible idea.
- MrOwnPut 4y agonope, not satire, is yours? you negged and put your opinion down, but you forgot to put down why it's "horrible"! so, until then... yes-huh!
- robofanatic 4y agowell, 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.
- MrOwnPut 4y agothe 10x designs the entire system. the 1x teams work in it after, in a controlled way. eventually the 1x teams understand the system and mimic the patterns. enough patterns created by the 10x it's hard for the 1x to fuck things up. yes you eventually won't have the 10x one day, but if you utilized them right, they made you a nice temple. 10x or not, if you have a team design a system you're doing it wrong. teams can work in it later, one person should design it.
- robofanatic 4y agofair enough. would love to see your work to really believe what you are saying.
- MrOwnPut 4y agounfortunately that would dox me and i love being a contrarian here apparently. feel free to shoot me a way to contact you if you want. but it's not really worthwhile for me to basically gather up a resume unless you have connections.