Code reviews (and standards) can also prevent cleverness (i.e.: actual code golfing in producton code). However, if the reviewer is not more experienced in the language, low performing or unnecessary constructs can still slip. I also think that there must a an automatic tool (like Perl::Critic) in the process. Btw, if you are implementing coding standards into the process, then it must be applied backwards on old code too IMHO. Lets say; if you forbid tabs, remove tab indentation from older code if it is still maintained. And column width is usually missed. I hate to see 500 chars on a code line (nope, word wrapping in an editor does not solve this shit).
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.