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.
-
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.
|