Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. Work Issues
  4. Programmer Output

Programmer Output

Scheduled Pinned Locked Moved Work Issues
c++toolsquestionworkspace
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Tom Thorp
    wrote on last edited by
    #1

    I'm been having kind of a running argument about programmer productivity in a c++ type environment about how many line of code a programmer should be producing. YES, I know that this is a hot topic with no good answers. However, I'm looking for suggestions about what would be reasonable number. I've seen stats saying about 9K/year. He is saying about 1k-2k/week of fully debugged code. I think that number is a "little" high. But I don't have any data to back that up. Anyone out there have an idea what a reasonable number is or where I can get some information?

    C L 2 Replies Last reply
    0
    • T Tom Thorp

      I'm been having kind of a running argument about programmer productivity in a c++ type environment about how many line of code a programmer should be producing. YES, I know that this is a hot topic with no good answers. However, I'm looking for suggestions about what would be reasonable number. I've seen stats saying about 9K/year. He is saying about 1k-2k/week of fully debugged code. I think that number is a "little" high. But I don't have any data to back that up. Anyone out there have an idea what a reasonable number is or where I can get some information?

      C Offline
      C Offline
      Colin Angus Mackay
      wrote on last edited by
      #2

      Tom Thorp wrote:

      He is saying

      Who is he? You've not mentioned this.

      Tom Thorp wrote:

      Anyone out there have an idea what a reasonable number is or where I can get some information?

      Well, it depends on what the developer's role really is. If they end up stuck in meetings for hours per week the KLOCs will go down. If they are a dedicated code monkey the number will go up (but, I'm betting the quality will go down) There is no answer to this question. It was a hot topic years ago and I really had thought it had dropped off the radar and crash landed somewhere. IMO it is not a valid metric to measure developer productivity.


      Upcoming events: * Glasgow: Mock Objects, SQL Server CLR Integration, Reporting Services, db4o, Dependency Injection with Spring ... "I wouldn't say boo to a goose. I'm not a coward, I just realise that it would be largely pointless." My website

      1 Reply Last reply
      0
      • T Tom Thorp

        I'm been having kind of a running argument about programmer productivity in a c++ type environment about how many line of code a programmer should be producing. YES, I know that this is a hot topic with no good answers. However, I'm looking for suggestions about what would be reasonable number. I've seen stats saying about 9K/year. He is saying about 1k-2k/week of fully debugged code. I think that number is a "little" high. But I don't have any data to back that up. Anyone out there have an idea what a reasonable number is or where I can get some information?

        L Offline
        L Offline
        Luc Pattyn
        wrote on last edited by
        #3

        What is a line of code ? Do these count: - empty lines (cosmetic reasons or other) - comment lines (I hope they count) - just a curly brace (the westcoast-eastcoast debate) And should your stats go up: - when duplicating code from one class to the next - when splitting a declaration with initializer in two lines ... And should your stats go down: - when you solve the job with fewer lines (by being more clever about it, not by putting more on a line);chances are there are fewer bugs. - when you find ways to reuse existing code ... etc. Hence, it makes no sense to me either.

        Luc Pattyn


        try { [Search CP Articles] [Search CP Forums] [Forum Guidelines] [My Articles] } catch { [Google] }


        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups