Those measurements seem to encourage one to develop and fix code quickly rather than carefully or efficiently, and to format code to use many lines.

Characteristics I might use:

• How easy is it to turn over a developer's code to another? Is it well commented? Is it clear what the code does and does not do? Is the code easily understood and adapted to other uses? Does it follow a style guide?
• Does the code include error checking and logging? How hard is it to recover from errors?
• How good is the boundary testing? By this, I mean to ask if the code scales well and handles the extremes of input data well. For example, a database export tool I inherited read all of a database into a hash tree and maintained all relationships in the database. The catch was that it stored the entire database in memory before exporting it to xml files. For any database with more than 50,000 users, the tool ran out of memory, making it useless for production systems.
• Does the developer create tools and practices that benefit others?

  ---

  In reply to Re: Measuring programmer quality by bwelch
  in thread 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":
  
  
  
  

  ---

• Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
• Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
• Read Where should I post X? if you're not absolutely sure you're posting in the right place.
• Please read these before you post! —
  • How do I compose an effective node title?
  • How do I post a question effectively?
  • Markup in the Monastery
• Posts may use any of the Perl Monks Approved HTML tags:

  a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

• You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

  	For:		Use:
  	&		&
  	<		&lt;
  	>		&gt;
  	[		&#91;
  	]		&#93;

• Link using PerlMonks shortcuts! What shortcuts can I use for linking?
• See Writeup Formatting Tips and other pages linked from there for more info.