While I haven't contributed to the P6 discussion for a while (thus, have no comment), this pet peeve is one that's shared by CPAN developers as well. Over the years, I've received a lot of "This is busted" bug reports. As I use nearly all my modules and it was broken, it's obviously a situation I hadn't run into yet. (If I had, it wouldn't be broken now, would it?!)

Since it's a situation I hadn't run into, what's the incentive for me to write the failing test that keeps the problem from returning? I'm not the one with the bug ... you are. The code is failing your expectations, not mine. By writing the failing test, you are forcing me to look at the bug. More importantly, you've given me a repeatable yardstick by which to measure my progress.

One of the biggest reasons Pugs such a success is because the developers of Pugs don't write tests. (Audrey is actually (in)famous for not writing them, much to my dismay.) They have a legion of test-writers who contribute hundreds and hundreds of failing tests. It is so much easier to write code to pass a series of tests than it is to write code that is just wandering out into the blue.

Moral of the story: If you don't like something, write a failing test. Let that be your bitchfest.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: No, "We" Don't Have to Do Anything by dragonchild
in thread No, "We" Don't Have to Do Anything by chromatic

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.