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? :)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.