I think it comes down to a level of responsibility, and trying to get past the egotistical angle that is easy to mistake. In my little world, we're pretty segregated in our sections of the code base. More than anything, when something goes wrong, I want to be held accountable if it's my "fault". Likewise, when something works well, I don't mind receiving a little praise..
If I am modifying existing code, for the love of bob comment vigorously, even if you don't sign your name to every line you modify, explain what the new code is doing.. Well documented code is a good thing!
cheers!
-
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.
|
