3 ms·
My guess here is that "programmer productivity" is probably the wrong measure. And that by trying to be reductive about that, you will probably miss somethng v
by ezy 17y ago
My guess here is that "programmer productivity" is probably the wrong measure. And that by trying to be reductive about that, you will probably miss somethng valuable...
My idea: what if we came up with an app idea and set two teams to it, with the only restriction being the language they could use (one Lisp, one "x"). The "winner" is the one who makes the most compelling app. Which one is most compelling can be decided in some arbitrary fashion -- My opinion is that it'll be fairly obvious (although I have no idea who would win out! Just to make that clear :-))
This doesn't sound so terribly scientific, does it? But I think that's about the best you're going to get if you want to measure the effectiveness of a programming language for a chosen task.
- tel 17y agoThat would undoubtedly be qualitative, though you're right that it's probably the closest thing to programmer productivity you can measure. I think you're wrong that reductionism can't find an interesting gem buried below. Productivity is something difficult to measure because it takes a long time and has a lot of influencing factors, but if you can split it apart just a little bit and lose some of the confounders you might be able to give at least a little quantitative foundation to claims shown anecdotally.