Mythical man month: 10 lines per developer day
blog.ndepend.com
Mythical man month: 10 lines per developer day
1–10 of 212 posts
Re: Mythical man month: 10 lines per developer day
#2Not quite sure what point the author is trying to make? He agrees that lines of code are a bad measure of productivity because, yet claims that the average he computes can help him predict future development times. Then he explicitly points out that different parts of the codebase required different amounts of work, apparently unrelated to their code line count, yet does not relate this to the previously mentioned points. Also, what is up with the random comment about code coverage at the end? That doesnt fit in with the rest of the article either...
Re: Mythical man month: 10 lines per developer day
#3Seems about right, on the average day, you put about 500 in. the average year later, you're lucky if 10 of those are left.
sits back waiting to be told how badly I suck and something about code churn and patterns
Re: Mythical man month: 10 lines per developer day
#4Over the last 2 months I’ve managed about 3k new loc and 90 classes, so that’s about 60ish lines per work day. I don’t feel like I was that productive though and spent a lot of time refactoring. Eg, last 1k lines barely added any features
What do you do to keep up a fast pace in a big project without throwing quality out? They say TDD increases your speed overall, according to a few case studies I found (15% longer to code, but 40% less bugs, so faster finish times overall etc)
Re: Mythical man month: 10 lines per developer day
#5What annoys me most about these metrics is that some days zero lines are written. Anything up to a month without results to show.
Where, then, does all this time go? Sometimes it's reading existing code. Sometimes it's learning about a new algorithm by reading blogs and papers. Sometimes it's developing test programs to iron out a bug or test out some new code.
There used to be one chap in the office that got all the hard problems - the seriously hard problems. Some of this was figuring out why USB couldn't transition from low-speed mode to high-speed mode reliably (USB is quite hard to probe due to frequency), or figuring out why the application crashed one in a million boots.
Some of our most valuable developers committed the least amount of code, but saved our arses more times than I can count.
Re: Mythical man month: 10 lines per developer day
#6A good measure is how many lines removed per day.
Re: Mythical man month: 10 lines per developer day
#7What annoys me most about these metrics is that some days zero lines are written. Anything up to a month without results to show. Where, then, does all this time go? Sometimes it's reading existing code. Sometimes it's learning about a new algorithm by reading blogs and papers. Sometimes it's developing test programs to iron out a bug or test out some new code. There used to be one chap in the office that got all the…
At one job, I replaced a 10k LOC class with a 20 line function which probably took me to a net negative loc count for that job.
Re: Mythical man month: 10 lines per developer day
#8Not quite sure what point the author is trying to make? He agrees that lines of code are a bad measure of productivity because, yet claims that the average he computes can help him predict future development times. Then he explicitly points out that different parts of the codebase required different amounts of work, apparently unrelated to their code line count, yet does not relate this to the previously mentioned po…
I am glad I am not the only one to scratch my head...
Re: Mythical man month: 10 lines per developer day
#93, take it or leave it.
Re: Mythical man month: 10 lines per developer day
#10If you are doing a good refactoring, you may have a massive negative LoC at the end.
LoC added or removed is not a very good metric for anything.
Except if I see a big negative number on a PR, it is usually a great thing. I still have to check what was removed but it usually mean that things are easier to understand.