The Linux development effort, Extreme Programming, and several other communities have bourne this out without neccessarily taking the same path of discovery. Peer review and letting a code snippet speak for its own quality are known to be good things. This gives us some additional insight into reasons why.
I actually think that there are other reasons why regular peer review of code is good, too. Sometimes, no matter how much ego you get out of the way, starign at the same problem too long just keeps you from finding the source of it. You look somewhere that looks like the source of the problem, build a conception in your head, and can't look anywhere else to find the bug. This particular problem happens even when you didn't write the code. Sometimes a fresh set of eyes is just needed to break you out of a rut.
Christopher E. Stith
-
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.
|
