I don't remember who said it, but there are the two basic rules of code developement:
- Make it run
- Make it run fast.
Once you have something that "works", release that to the User and let them work with it for a while. They are the arbiters of whether the solution is 'fast enough'. If they are happy with it, you are done; even if you could coax an extra 20% reduction ibn the run time if you only ....
That said, there are some problems where the scale is such that you can't have too much performance. As an example, think about processing the Apache logs for the likes of Yahoo or Google or Amazon. If they aren't (individually) producing 100's of gigabytes of logs per day, I'd be most highly supprised. Problems on this size *are* worth tweaking every bit of performance -- a 0.001% reduction in the amount of time it takes to process 1000 log messages translates at that scale to over an hour reduction in the process.
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.