The fastest script in the world is worthless if a change in your
system's directory structure breaks your code and you can't fix it.
If you bother to optimize for anything, do it for maintainability
But never forget "monitorability".
Unless your script is being called to do huge jobs, or your resources
are very restricted (Sparc Ultra 1 or Intel 486, etc.) optimization for
speed is not usually that big an issue.
However, thorough and correct logging of events, meaningful commentary
in the script itself, reusability of the code; these will all help
with maintainability.
-
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.
|
