Example: I had some large csv files to import into a rails app. Instead of writing my own importer and running it with script/runner, I scripted a quick importer ontop of mysqlimport. Mysqlimport ran about 1000x faster than a custom solution.
I guess this averages out. Just that some people seem to have incredible mental stamina.
You don't win a race by "driving fast", you win a race by never driving slowly. It doesn't matter how fast your car is if you spend 30% of your time stacked up at intersections.
Similarly, programmers spent a lot of time dealing with various barriers to productivity. (For instance, bugs you can't fix) If you want to increase your productivity, you need to attack these barriers by every means necessary.
Of course, there's some real variation in the averages that people will settle down to over the course of hundreds of debugging tasks, but an individual's productivity on debugging tasks varies so much that I'd be hard pressed to say much at all about the individuals until I'd seen them do at least a few trials.
It may be the case that the differences in the average times people take do end up being on the order of 10x or more, but it would take a lot of observation to say that for sure (exactly how much depends on what sort of distributions we see when we measure this stuff).
Interestingly there are articles out there which suggest that one distribution (of competence, rather than productivity, but intuitively you'd expect the two to be related) is actually bimodal rather than normal, "the camel has two humps":
http://www.codinghorror.com/blog/2006/07/separating-programm...
Since when did testing and deploying become "unproductive work"? If getting reliable, tested code in front of customers is not your job, what is?
Old school people might call it getting stuck in a rut. It's much easier for me to get stuck in a rut doing testing and documentation, compared to doing something new and exciting.
I'm curious as to whether developing automated testing and deployment stuff would count as doing testing and deploying, or as developing exciting new stuff.
And for me, developing the automated stuff is still not particularly interesting. I guess if I were designing cars, my interests (and thus most productive department) would lie with building the car itself (engine, body, drivetrain, etc.) rather than the safety system or QA. Maybe it's just my personality.
It's nominally true because many programmers have zero or lower productivity, sometimes due to no fault of their own. If you work on a project for three years, and then it gets canceled, you could say your work had no economic value because it never got in front of customers. If some PHP hack manages to pound something out in a month that brings in $100,000 of business, he looks like a hero, no matter how bad the code is.
In my view, superproductivity is about alignment with your environment. If you work for 12 months a year, but spend 3 of them on side projects that go nowhere, spend 3 months being a sysadmin, and then waste another 5 months on reworking a GUI, there goes about 90% of your productivity.
The "Mythical Man Month" says that about 20% of the time on a software project is spend coding, the rest is requirements work, testing and that kind of stuff. A superprogrammer with supertools might be able to do that in time that approaches zero asymptotically, but unless you can get rid of the other 80%, project cost and time don't get much worse, even in comparison with a coder who is half as productive as average.
The moral? If you want to look like a genius, find some place where (i) requirement work takes little time (and wastes little time downstream with changes) and (ii) testing, deployment and all that is minimal.