I liked dragonchild 's two points. I'd add that the number of defects can be completely arbitrary because a spec can leave out all the behavior the tickets/defects represent.

E.g., at my current gig, the specs for product features are usually sentence fragments. I kid you not. Asking for more details produces the response: "We don't have time for that right now." From that sentence fragment the dev is to intuit everything that needs to happen. My first two word ticket there ended up taking three CGIs, a bunch of rewritten PHP, a moved/rehosted website, a patched CPAN module, some JavaScript, and a 16 hour day to catch up with what was ostensibly a "gimme."

I do wish you could measure dev quality because I've seen a few idiots/slackers become managers and wreck dev teams or projects. I think time and money are the only real measures though. Mmmmm… No, posts on PerlMonks count too. If I were running a company there are at least 15 monks here I'd hire at any rate I could afford without so much as an interview. In fact, at least a couple of them have already responded in this thread. :)

In reply to Uncrackable nuts by Your Mother
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! —
  • 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:
    & &amp;
    < &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.