News for hackers. Stuff that matters.
Re:Fact and folklore in software engineering by PaulHoule on Wednesday January 05, 2011 @03:19PM (#2072311)
I think the "10x" myth persists because we all imagine that we're the programmers who are "10x" better than average.

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.

Re:Fact and folklore in software engineering by varjag on Wednesday January 05, 2011 @03:31PM (#2072352)
On some weeks, I am 10x.. no, scratch that, 50x more productive than myself on the others. And I've seen some people who are capable to sustain that indefinitely.
Re:Fact and folklore in software engineering by idoh on Wednesday January 05, 2011 @04:18PM (#2072514)
Can you flesh that out a bit - any thing interesting that you did?
Re:Fact and folklore in software engineering by michaelbuckbee on Wednesday January 05, 2011 @04:32PM (#2072580)
I think the big productivity improvements are those that in retrospect just seem like: "Yeah, that was the right way to do things."

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.

Re:Fact and folklore in software engineering by varjag on Friday January 07, 2011 @10:25AM (#2079756)
Well when it concerns yourself it's a bit easier to gauge performance. I'm an embedded systems developer, sometimes able to write 5 device drivers in 5 days, but on others barely able to begin, let alone complete, even the most trivial tasks.

I guess this averages out. Just that some people seem to have incredible mental stamina.

Re:Fact and folklore in software engineering by lispm on Wednesday January 05, 2011 @03:38PM (#2072368)
I have seen programmers that are more than ten times faster than some slow programmers. There are debugging tasks where some people struggle for days, while others would find it in one hour.
Re:Fact and folklore in software engineering by PaulHoule on Wednesday January 05, 2011 @03:48PM (#2072417)
Sure, which leads one to thinking about it like auto racing.

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.

Re:Fact and folklore in software engineering by ewjordan on Wednesday January 05, 2011 @05:40PM (#2072864)
Take any non-trivial debugging task (i.e. something that slipped through the net for several releases in a live system, not a simple bug in fresh code) and set me on it 100 times, and you'll almost definitely see at least 10x variation in how long it takes me, and that's just because of the nature of debugging, sometimes you get lucky and sometimes you don't.

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).

Re:Fact and folklore in software engineering by Morendil on Wednesday January 05, 2011 @06:24PM (#2073038)
Kudos for pointing out that it's the shape of the distribution that matters, not how far apart its endpoints.

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...

Re:Fact and folklore in software engineering by pyrhho on Wednesday January 05, 2011 @04:33PM (#2072584)
> (ii) testing, deployment and all that is minimal.

Since when did testing and deploying become "unproductive work"? If getting reliable, tested code in front of customers is not your job, what is?

Re:Fact and folklore in software engineering by Travis on Wednesday January 05, 2011 @06:57PM (#2073139)
It's not that it is unproductive (for me), but rather that it feels like drudge work. Which makes me less motivated to do it, which negatively influences my productivity on other parts of the project. I think we can add documentation to this as well.

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.

Re:Fact and folklore in software engineering by pyrhho on Thursday January 06, 2011 @04:32AM (#2074721)
Fair enough, but classifying something as "unproductive" just because you don't enjoy doing it seems a bit... incorrect.

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.

Re:Fact and folklore in software engineering by Travis on Thursday January 06, 2011 @11:50AM (#2076018)
Sorry, just to clarify a bit: it's not that I consider it unproductive because I don't like it, but because my personal productivity is much less for projects I am less engaged in. So I'm less productive due to the nature of the work.

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.

Re:Fact and folklore in software engineering by jsvaughan on Wednesday January 05, 2011 @03:41PM (#2072386)
it's unfortunate but true that a small handful of developers have zero or lower productivity because they are incompetent.