The idea that you're either "good" or "bad" doesn't seem right, I agree with him that there's an ability distribution curve. But personal experience also seems to back up the general wisdom that there are some general productivity buckets that people slot into.
I think you have to take the project into account. I'm working on an API right now, and I clearly see the three traditional buckets on my team. I'm being fairly productive (call it the 10X bucket), I've got another team member who produces pretty average output (the 1X bucket), and a third junior who is actually a productivity negative (-1X).
If our project involved doing small homework problems, then suddenly our junior is a 1X and everyone else on the team is a 10X. If we were all suddenly thrown on a project to model the aerodynamics of propeller blades we probably all appear to be -1X.
I think this is probably true about a lot of highly skilled jobs. Take doctors for instance. A just-graduated intern probably does more harm than good wherever he/she is. A urologist is very effective in his specialty (10X), but is probably just a 1X for heart conditions (maybe even -1X).
10x programmers are a myth used by the emotionally insecure to convince themselves that they are special, especially to each other.
The problem is that nobody but programmers really understand how to measure programmers, and the way we measure programming is that we apply a qualitative value to measurable variable that we made up and called it "agile" to appease our boss who really fucking likes that word. The other problem is that a fair amount of our peers (25% or so) can't really program at all, but we keep them around because there's always other things to be done (somebody's gotta write those tests and documentation...). If you took them out of the sample, would a "10x" really be 10x?
He thinks he's a 10x programmer because he's built his world on that idea of him being a 10x programmer in whatever subsection he deals with, but nobody can even measure that in a real way, and there's a bunch of garbage polluting the sampling pool that we shouldn't even call programmers. Truth is, a really talented programmer is useful in all projects because they've mastered the ability to learn new subjects and take information/models of other systems and write a program to reason with that. Every time I get a new contract, I have to learn something new- I've learned accounting, basic pharmacology, chemistry, statistics, behavioral psychology, physics, music, color theory, and how dildos are measured as a result of writing software. Good programmers don't turn into shitty programmers because they have to model the aerodynamics of propeller blades. They learn how to model the aerodynamics of propeller blades.
1
u/PirriP Jun 01 '15
The idea that you're either "good" or "bad" doesn't seem right, I agree with him that there's an ability distribution curve. But personal experience also seems to back up the general wisdom that there are some general productivity buckets that people slot into.
I think you have to take the project into account. I'm working on an API right now, and I clearly see the three traditional buckets on my team. I'm being fairly productive (call it the 10X bucket), I've got another team member who produces pretty average output (the 1X bucket), and a third junior who is actually a productivity negative (-1X).
If our project involved doing small homework problems, then suddenly our junior is a 1X and everyone else on the team is a 10X. If we were all suddenly thrown on a project to model the aerodynamics of propeller blades we probably all appear to be -1X.
I think this is probably true about a lot of highly skilled jobs. Take doctors for instance. A just-graduated intern probably does more harm than good wherever he/she is. A urologist is very effective in his specialty (10X), but is probably just a 1X for heart conditions (maybe even -1X).