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.
Hope this is satire. Otherwise its a horrible idea.
you negged and put your opinion down, but you forgot to put down why it's "horrible"!
so, until then... yes-huh!
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.
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.
a lot of the cool stuff in my later years is commercial.
you could have just replied with your contact info if you were really interested in me.
the only reason for me to try to prove anything to you would be if you were actually someone.
This idea of a surgeon team is also from Brooks.
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
i don't need an e-diagnosis from a few sentences of mine though, thanks.
i know what i make and what others make and how easy it comes to me. the label doesn't matter.
i tamed my mind and my environment long ago, any thematical "adhd" attributes concerns me not...
my sake thanks you for your hope though.
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.