I, for one, see nothing wrong or evil about this. I believe that I remember reading something similar to this on Joel On Software. His take was that you should bury poor programmers on your team with bug reports. The result is that they will either improve or leave.
Also, regarding some of the other comments above, just because someone is on your team doesn't mean they should not be held responsible for the problems they cause. Adding additional tests is somewhat of a backdoor way of making them responsible, but, if all else fails, I'd think it is a very appropriate way to get someone's attention to their poor code.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||