How many lines of code per day should a good programmer produce? - c++

This is a discussion on How many lines of code per day should a good programmer produce? - c++ ; I know this is very much dependent on complexity etc but is there a standard benchmark number of lines of code that a reasonably experienced C++ programmer produces per day. I reckon on a good day I can knock out ...

+ Reply to Thread
Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 21

How many lines of code per day should a good programmer produce?

  1. Default How many lines of code per day should a good programmer produce?

    I know this is very much dependent on complexity etc but is there a
    standard benchmark number of lines of code that a reasonably
    experienced C++ programmer produces per day. I reckon on a good day I
    can knock out 200 lines. Is that good? Bad?

    Or is this benchmakr a bit of a waste of time?

    I know this is a bit of topic but I am genuinely interested. And no I
    am not a troll.


  2. Default Re: How many lines of code per day should a good programmer produce?

    Angus wrote:

    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day.


    The juniors around me can write 30 to 40 lines per day, but I'm a grizzled
    senior so I only write like 5 or 10.

    --
    Phlip
    http://www.oreilly.com/catalog/9780596510657/
    ^ assert_xpath

  3. Default Re: How many lines of code per day should a good programmer produce?

    Juha Nieminen wrote:

    > What counts is the *quality* of that code, not its amount. I would
    > prefer doing 200 lines of extremely high-quality code in 1 week than to
    > make 500 lines of crappy code in one day.


    I delete 20 to 50 lines of code per day...

    --
    Phlip

  4. Default Re: How many lines of code per day should a good programmer produce?

    Angus wrote:
    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day.


    If this is a question (I would have liked a question mark at the end
    of one), then the answer is "no, there isn't".

    > I reckon on a good day I
    > can knock out 200 lines. Is that good? Bad?


    It depends. Show us what you "know out", and we can tell. Of course,
    in order for me to review your code, I need to be compensated. And,
    no, a sample 200 lines won't do. You need to show us at least 2000 LOC
    to make the review meaningful.

    > Or is this benchmakr a bit of a waste of time?


    A benchmark is a benchmark; once obtained it might have its use some
    day. However, without a target use, obtaining such a benchmark _can_
    be viewed as a waste of time. And I don't think there is such a thing
    as "a bit of a waste of time". It's either a waste of time or it is
    not.

    > I know this is a bit of topic but I am genuinely interested. And no I
    > am not a troll.


    Try posting to 'comp.software-eng'. That's where discussions like this
    belong.

    V
    --
    Please remove capital 'A's when replying by e-mail
    I do not respond to top-posted replies, please don't ask



  5. Default Re: How many lines of code per day should a good programmer produce?

    On Oct 2, 2:29 pm, Angus <anguscom...@gmail.com> wrote:
    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day. I reckon on a good day I
    > can knock out 200 lines. Is that good? Bad?
    >
    > Or is this benchmakr a bit of a waste of time?
    >
    > I know this is a bit of topic but I am genuinely interested. And no I
    > am not a troll.


    How long is a piece of string?

    There are many levels of quality of computer code. Stuff
    that that is intended strictly for personal use, on a "code
    and forget" kind of basis would probably be the lowest.
    You write something to do a task, finish the task, and
    forget the code. When you do that sort of thing, 200
    lines a day isn't bad. But the expectation is, the quality
    will be low. You might do this sort of thing when, for
    example, you had one 10 megabyte file that needed some
    complex reformatting. Say you needed to migrate *one* old
    file to a new spec on a new system.

    The next level is code that gets passed between developers,
    never gets sold, and is only documented at the most trivial
    of levels. Often as hand-scribbled notes, photocopied and
    passed along with the source. That would be logon scripts
    and the like.

    The next level is a minimal "internal to the company"
    package. It has a formal documentation set, but only of
    a minimal sort. It has some level of testing and QA. The
    product is still only intended for other developers, but
    now it's a (slightly) formal product. This is about the
    level of Gnu "for developer" products. Users are expected
    to have some degree of expertise in the subject, and make
    significant effort to use the app.

    The next level is a sem-formal product.
    It gets some official docs, testing, QA, etc. And there is
    a user manual intended for use by non-developers. This is
    about the level of typical shareware products. Users are
    expected to have some sophistication, but are not expected
    to do any significant "under the hood" sort of stuff.

    The next level is a commercial product released for the
    general public. It has formal specs, user manual, testing,
    QA, install scripts, self diagnostics, etc. All the stuff
    you need to "shrink wrap" a product.

    Each of these steps is expected to multiply the effort
    "per line" by about a factor of 3. Though, the farther
    along you go the more non-developers can be used to help
    do the work.

    Typing in 200 lines of code isn't a big deal. The hard
    effort, the time consuming stuff, is the design of the
    app, including the spec, the testing schemes, the
    prototypical data sets, the general architecture, and
    so on. Other quite time intense tasks are testing,
    documentation, QA, and such like.

    Generally, commercial code usually takes something round
    about one person hour per line of shipped code.
    Socks


  6. Default Re: How many lines of code per day should a good programmer produce?

    Angus wrote:
    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day. I reckon on a good day I
    > can knock out 200 lines. Is that good? Bad?
    >
    > Or is this benchmakr a bit of a waste of time?


    Counting programming productivity by number of lines written is
    completely nonsensical.

    What counts is the *quality* of that code, not its amount. I would
    prefer doing 200 lines of extremely high-quality code in 1 week than to
    make 500 lines of crappy code in one day.

    Of course measuring the quality of the code is pretty difficult, so
    even trying to benchmark productivity is quite difficult.

  7. Default Re: How many lines of code per day should a good programmer produce?

    On Oct 2, 8:29 pm, Angus <anguscom...@gmail.com> wrote:
    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day. I reckon on a good day I
    > can knock out 200 lines. Is that good? Bad?


    I don't know. All I can say is not too long ago there were to
    programmers in our team (they did one of our GUI's in QT) that
    could produce an immense amount of code by cutting an pasting (They
    were not exactly in my team, so I realized this too late). The
    managers were mighty pleased and the GUIs were quite impressive
    at first. Then the client required changes. I noticed that
    the one guy always burnt the midnight oil. Now I know why.

    OTOH I recently (very recently) worked with a guy that opened
    my eyes wrt. template metaprogramming. This guy could literally
    generate code. He had the ability to think recursively to the
    point where I became frustrated with myself. He also had the
    ability to hide the ugly tmp things quite nicely. Took him
    about a week to write a hundred lines (maybe I'm exaggerating
    here). He could handle requirements changes quite quickly as
    well. Nevertheless, I did not like maintaining his code.

    > Or is this benchmakr a bit of a waste of time?


    What does one want to achieve with a benchmark like this? You could
    probably compare the complexity of projects, but there as so many
    other
    variables. I suppose this could be a variable, but in general I think
    managers over-estimate its value (especially for C++ code).

    Regards,

    Werner


  8. Default Re: How many lines of code per day should a good programmer produce?

    On Oct 2, 7:29 pm, Angus <anguscom...@gmail.com> wrote:
    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day. I reckon on a good day I
    > can knock out 200 lines. Is that good? Bad?
    >
    > Or is this benchmakr a bit of a waste of time?
    >
    > I know this is a bit of topic but I am genuinely interested. And no I
    > am not a troll.


    LOC is bollocks.

    Debug-build object code size (given a specific CPU) can be meaningful,
    but only after all testing (including integration) has been passed.

    Habitual cut-and-pasters must be terminated with extreme prejudice.


  9. Default Re: How many lines of code per day should a good programmer produce?

    Angus <anguscomber@gmail.com> wrote:
    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably
    > experienced C++ programmer produces per day. I reckon on a good day I
    > can knock out 200 lines. Is that good? Bad?


    On a *good* day I *remove* LOC, sometimes in the hundreds.

    > Or is this benchmakr a bit of a waste of time?


    Quite. It's not that hard to generate *huge* LOC in a day. Sometimes
    the LOC produced are actually useful and appropriate for the problem.


    Keith
    --
    Keith Davies "History is made by stupid people
    keith.davies@kjdavies.org "Clever people wouldn't even try
    keith.davies@gmail.com "If you want a place in the history books
    http://www.kjdavies.org/ "Then do something dumb before you die."
    -- The Arrogant Worms

  10. Default Re: How many lines of code per day should a good programmerproduce?

    On Tue, 02 Oct 2007 11:29:40 -0700, Noone wrote:

    > I know this is very much dependent on complexity etc but is there a
    > standard benchmark number of lines of code that a reasonably experienced
    > C++ programmer produces per day. I reckon on a good day I can knock out
    > 200 lines. Is that good? Bad?
    >
    > Or is this benchmakr a bit of a waste of time?


    The answer is...zero! A good programmer will reuse previous work and
    avoid programming if at all possible.

    Many years ago folks tried to measure productivity by number of lines of
    bug-free code written, but the metric is pretty useless when you consider
    that it's not all about writing a lot of code.

    I'm more interested in the design methodology used: did the SE properly
    ****yze the task? did they research proper reuse of existing code/
    systems? then, how simple and elegant was their solution?



+ Reply to Thread
Page 1 of 3 1 2 3 LastLast

Similar Threads

  1. Replies: 2
    Last Post: 12-10-2007, 12:40 PM
  2. VBA code to produce random passwords
    By Application Development in forum ADO DAO RDO RDS
    Replies: 1
    Last Post: 10-16-2007, 06:29 PM
  3. Can this code be modified to produce a 16-bit grayscale file
    By Application Development in forum DOTNET
    Replies: 4
    Last Post: 09-09-2007, 08:15 PM
  4. Easy question for a good programmer...
    By Application Development in forum Javascript
    Replies: 3
    Last Post: 08-12-2007, 03:44 PM
  5. Using Ildasm to produce buildable source code
    By Application Development in forum DOTNET
    Replies: 3
    Last Post: 03-22-2005, 01:07 AM