It really depends on what you're doing... people who don't actually work in the field tend to not understand and assume us code monkeys just knock 'em out as fast as we can type them. Those who actually tend to do this are normally producing terrible code.
I wouldn't say it's 3-5 lines per day... first of all "lines" is a terrible measure for code. You are significantly better off measuring "statements" because that is more specific and overall more comparable between languages. I would say a programmer tends to output somewhere around 50-100 quality statements per work day (8 hours). That is to say, statements that actually mean something... this would ignore simple control statements such as conditionals, loops, etc...
To write real code, it requires real planning, and real thinking... some days, I might write 1000 lines of code and other days I might write 0... it all depends on what I'm doing and what I'm trying to accomplish. Overall, no matter what you're doing, it should all be equally productive if you plan to keep your job.
EDIT: You're giving people thumbs down because you don't know how to phrase a question and are inable to understand why it's a silly question in the first place? The metric is useless... nobody would measure "lines of code" to grade productivity which is what your topic is looking for... learn to ask a question before you make demands on those that are helping you.
· 1 decade ago