6/2/03 2:54:21 AM, Wouter van Ooijen wrote: >> > I think I read somewhere that 20 lines a day in >> > assembly is expected? >> >> That is totally rediculous. That means it would take 2 1/2 >> man-months to write just 1000 lines! > >It just depends on your definition or 'write'. It might include >everything from pre-sales consultancy to in-field troubleshooting. I can >krank out a few 1000's of lines in a day, but that is not the same thing >as making it into a product. Exactly. The "20 lines per day" figure is based on dividing the number of lines of code *in the final deliverable* by the number of days spent on *all aspects* of the program, *not* just the coding phase. So the numerator doesn't include things like test-harness code, or code that had to be scrapped because of requirements changes, and the denominator includes a lot more things than coding (testing, debugging, documenting, design, requirements analysis, administrative stuff, progress reporting, etc). It does *not* mean that someone can't code more than 20 lines in 24 hours, any more than "the average family has 1.5 children" means that any family has a child with a partial body. You'd get very similar figures, by the way, if you divided the number of words in a book by the number of days it took the author to write it. You have to account for all the time spent outlining, writing first drafts, etc. -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu