Skip to main content
Skeptics

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

24
  • 3
    I had quick search through the book. I cannot find any claim of this form. He does reference some studies of lines-per-year. Please include a quote of the claim from the book, so we are not targeting a strawman. As this is going to attract poor answers before this is resolved, I am putting on hold. Commented Aug 6, 2013 at 10:28
  • 3
    There's a lot of data on this subject, with references, in amazon.com/Software-Estimation-Demystifying-Practices-Microsoft/… I don't have my copy of that book with me, but I copied the following data from it two years ago: For a project whose size is between 1000 and 100,000 lines of code, expect from 400 to 833 lines of code per month. Effort varies non-linearly with project size and complexity, but 400 LOC/month is in the same ballpark as 10 LOC/day. Note that this estimate of average LOC/day includes the project's non-coding activities, for example ... Commented Aug 6, 2013 at 10:59
  • 2
    The question now has appropriate quotes for notability. Thank you. Let's take the rest of the discussion about notability demands to chat or meta. Commented Aug 6, 2013 at 13:20
  • 3
    @DJClayworth The 'seminal book' was first published in 1975. IMO a good answer would say whether the quoted metric is still true today, and state the sources of the (more recent) data, instead of simply 'appealing to authority'. Commented Aug 6, 2013 at 15:29
  • 9
    @user357320 You're forgetting to factor in the lines that are written but don't make it to the final product. When programming a project I could very easily wind up writing 300 lines of code in the space of two hours, then spend the rest of the week and next week debugging, tweaking, yelling at the compiler, realizing that two of the functions I'd originally written won't actually work, then erase half of them and restructure the rest into something that /does/ work. End result: two weeks of work, 150 lines of code. Commented Aug 9, 2013 at 13:06