On average, how many lines of code should developer write per day?
I want to know how to answer this question.
Measuring programming progress by lines of code is like measuring aircraft building progress by weight. -- Bill Gates
Jake Petroules
2010-08-08 05:09:51
+1
A:
Some days you'll net none, other days you may net a few hundred. Depends heavily on the project, and the people involved.
jer
2010-08-08 05:07:17
Since I use the headfirst strategy in web development, its usually a day of writing tons of code, and a day of debugging with little lines of code
TheLQ
2010-08-08 05:09:54
+2
A:
LoC is not an accurate way to describe productivity. It doesn't take into account how much work has been done, just how much your codebase has bloated. http://www.folklore.org/StoryView.py?project=Macintosh&story=Negative_2000_Lines_Of_Code.txt
Matt Williamson
2010-08-08 05:07:39
A:
That depends on so many factors it's impossible to give a general answer. Plus, how do you define "should"? Lines of code are also a poor measure of progress anyways...
Jake Petroules
2010-08-08 05:08:45
+2
A:
I once wrote 500 lines of code in one day, then went to sleep and realised that what I had written is overly complicated and stupid. I woke up the next morning and wrote 100 lines of code that replaced my 500 lines and was way faster and more efficient. Work smarter, not harder.
Marko
2010-08-08 05:09:59
+1, I actually did that twice on one the same module of one project!
Jake Petroules
2010-08-08 05:11:06