It's just taken me 30 days to add some new CLI functionality to a piece of code (my first ever time working with this bit of the code stack - I'm not familiar with the underlying code, the debug tools, the various ways the build can fail). I know that the standard time for an experienced CLI developer to implement the equivalent extension of functionality on this section of the code is 3 days.
My second piece of CLI functionality is on track for 15 days... so by the time that's finished I will only be 5 times worse. :)
An interesting data point he cites is the comparision between Lotus 123 version 3 and Excel 3.0: "Excel took 50 staff years to produce 649,000 lines of code. Lotus 123 took 260 staff years to produce 400,000 lines of code. [...] The difference in productivity between the two teams was more than a factor of 8." But then it will probably not be too difficult to find people who will tell you that 123 was still the better product.
[Edit: Another important point is that the these factors are between the best and the worst. The difference between the best and the median can be considerably smaller, so it is not that surprising not to see any programmers paid ten times the average.]
http://www.amazon.com/Peopleware-Productive-Projects-Teams-S...
I would paste some quotes but I lost my copy.