Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Dear Monks,

I've been thinking about this one for a few days, mostly because I've moved from a systems admin-centric role into a more pure development role. I'm trying to find a way to baseline and measure my output/performance while focusing on quality as the critical component. This is really for personal enrichment, but if its useful to others then great.

This is a general dev question of course, but since most of my development is in perl, I thought it relevant to my favourite bunch of perlheads :)

What metrics does one use to measure a programmers 'quality' or 'kwalitee' of output ? I can envisage a series of normalized metrics, each of which has to reach a minimum passing value, and then a weighted mean of them all would constitute a 'grade'.

Things I'm thinking are :

  • number of defects opened against your code over time
  • numbers of defects closed over time
  • number of lines of code added per defect fixed
  • number of lines of code *removed* per defect
  • number of lines of code made into reusable modules
  • average 'time to fix'
  • number of unit tests written per subroutine
  • ...

I'm referring here of course to internal company code, and not CPAN code, which has its own well developed standards as I understand it.

How these all hang together I'm really not sure yet. Thus, I open it to the floor for discussion :)

Thanks for your time and consideration.

In reply to Measuring programmer quality by deorth

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others learning in the Monastery: (4)
As of 2024-03-29 00:57 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found