It is for that reason that I think everyone should spend a while writing in assembly language. I spent some time doing graphics demo coding for fun, and it has given me a deep insight into the inner workings. Of course, you're not going to do much work in assembler, but you get a fine feel for efficiency.
Even though you're miles above that level when writing Perl, it gives you a sense for what approaches generally are efficient, so even when you're not trying to squeeze cycles out of your code (and most of the time you shouldn't, you should be coding for maintainability), you are instinctively economical. It simply sharpens one's senses.
Makeshifts last the longest.
-
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.
|