What I'm interested to know is ...
- how do other Monks go about optimising their code?
Until I know that there's really a problem, I don't.
If there is a problem, then measure before making any code changes. Sometimes the optimization is where you think it is, but much of the time it won't be. Then measure again.
- when faced with more than one obvious way to do something, what's the determining factor?
Pick the way that's clearer. Code has multiple audiences: one audience is the computer, another is the person who picks up the code next. I try to make sure things are correct for the former, and clear and concise for the latter. If you write all of your code with the assumption that it might be tacked up on a wall for passers by to comment on, you won't go too wrong.
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.