I agree wholeheartedly with this meditation, but wish to add a word of caution. I generally relish peer review and comments about coding, algorithms etc. However, in a recent project an "expert" from outside the team was called in. He looked over the project and said, "use this structure instead". When I objected that his structure had faults a, b and c, he said, "think of egoless programming". His point was that clearly I could not see the faults in my own design. In fact, he spoke out of his lack of understanding -- his design was mildly easier to implement, but provided significantly reduced functionality. Occasionally, disagreement may be based in reality and not just ego protection.
We have to be cautious of this and seek not just one but a broad range of opinions. This is true not only when others disagree with us, but when they agree as well... We also have to be open to suggestions of alternatives.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.