4 ms·
The same person might be a 1x or 10x developer, depending on the rest of the team. You also need to include politics, experience, processes and many other rela
by mgkimsal 7y ago
The same person might be a 1x or 10x developer, depending on the rest of the team. You also need to include politics, experience, processes and many other related bits which can have an impact on how much a potential '10x' dev can actually contribute (indeed - how is the 1-10x measured in the first place).
I had an 18 month period where I was, essentially, a "10x" developer, and a "1x" contributor. My skills didn't radically change in that time period. What changed was the environments and teams I was in. I wouldn't be a '10x' in every team/environment, and I'm not sure that anyone can.
- sombremesa 7y agoYou can also be a 100x programmer, since it's all relative. That's not a very fun way to work though (depending on your personality of course) - you just end up relegated more to mentoring and training than actual development. That being said, there are definitely people who have a knack for it and can learn fast, and also people who are just not cut out for it, period.
- tempguy9999 7y agoAgreed. I'm a 1x guy, but my knowledge is considerable. Put me in a team where I can share that knowledge and I get valuable. The more bods I can share it with, the greater the value I can bring and it's demonstrably a lot. However I'm not an engine that does the work, more like a lever that others can use to multiply their lifting capacity. My weakness is I assume everyone around me is as open to (constructive) criticism as I am, and willing to learn from it. This proves often not the case. tl;dr I rub people up the wrong way. This reduces my worth.
- Vinnl 7y ago> My weakness is I assume everyone around me is as open to (constructive) criticism as I am, and willing to learn from it. This proves often not the case. tl;dr I rub people up the wrong way. This reduces my worth. Of course another explanation might be that - your criticism is not constructive - your knowledge might not always be relevant - you might not have as much knowledge as you think - the incorporation of your knowledge might not be what's best for the organisation at that point (e.g. the time investment might not be worth it) - something else There's no way to tell for us here, but do not automatically assume that the problem is other's willingness to accept criticism (or your ability to make them accept it). It might be the case, but it might not.
- tempguy9999 7y ago> your criticism is not constructive It always is. I never criticise destructively. > your knowledge might not always be relevant Then I expect to be told "no, you're wrong, here's why..." and then we can discuss, and one or both of us can learn something. > you might not have as much knowledge as you think Always true! However if the other can indicate areas of ignorance, I appreciate that and will go away and learn about it. > the incorporation of your knowledge might not be what's best for the organisation at that point I see my job as supporting the business. I happen to do that with technical tools, but that doesn't change the fact that I'm there to support the company because it pays my wages. > something else Probably I'm just insensitive/thoughtless and should learn to think before speaking. But definitely a fair fraction of programmers get defensive about their code. Anyway, good points, upvoted.
- mgkimsal 7y agoFWIW, what I'd meant was I was both a 1x and a 10x at different points. I saw 'developer' and 'contributor' there, and that was a mistake. I'd meant to use the same word in both cases, an emphasize the 1/10 difference. Apologies if that caused any confusion.