I agree that there's the danger of advice being taken as gospel, as you put it. FWIW, I don't ask that anyone substitute my judgment for theirs, and I don't by any means think there is One True Rule on how to go about things. The only One True Rule is: think about what you are doing and use your best judgment. I simply felt that if I'm going to take a position in the meditation, it should be consistent. I wanted to offer food for thought, and so I presented my reasoning as directly as possible. As I've mentioned elsewhere, I've mainly been in situations where these arguments make sense: my systems don't get pushed to more than a handful of servers and accounts, and my organization's policies give me wide latitude to choose what software I need to accomplish the task at hand. Someone else would be much better qualified to write the contrary meditation on Top N (Good) Reasons Not To Use Modules. Maybe JavaFan? :)
-
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.
|