Your comment:
I believe this allows Perl to be regarded as a tool for expressing one's creativity and culture while still doing his/her job. This is unarguably a good thing.
Hmmm. I am not sure I totally agree with you here. When managing a large development project, with 20 developers involved, the last thing I want to manage is individual programmers expressing their "creativity and culture" in strange ways. (I recall one programmer who would intersperse his code with latin comments.)
Imagine that a year or two in the future, you are the sole maintenance programmer for a system developed by ten programmers all given full rein to their individual expressions of creativity and culture. All the more reason for enforcing a site standard in style and structure.
Of course, in a well managed team, peer reviews and code walkthroughs should remove the most extreme cases of wierd individual style.
-
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.
|
