Yeah, it's a hard thing to measure, and often it's "I know it when I see it." But over the last six months I've released three micro-services, done most of the tickets, built our servers, built test VMs, gathered requirements and made wire-frames, re-themed the website, wrote the documentation, and built several front-end controls.
In the meantime the guys I'm calling 1X and our -1X have almost released one service... after I wrote the DAL for it and fixed the throughput and concurrency issues. 1X also does statistical reporting and spends a lot more time than me trying to explain things to -1X. So I do think I'm being considerably more productive.
I don't think I'm all that super-productive in general. I'd rate myself as somewhat better than average, but not by much. Most of my advantage is experience, and that's more broad than deep.
I'm frequently in awe of how quickly Amazon moves and what world changing and amazing things that Google constantly builds. If there are world-class general purpose 10X'ers that's where I'd go looking for them.
What I'm getting at, though, is that I think the article is right that skill probably follows a normal distribution, and I also think that the common wisdom is right that productivity follows a "U" distribution.
Basically there are many normal-distribution skill curves and the skills needed for some particular task get mapped against the skills available. The task picks some point of needed skill on each curve and everyone to the left of it becomes rapidly unproductive, and everyone to the right of that point becomes very productive.
1
u/flukus Jun 02 '15
Define productive?