This may sound like vaguely inane advice, but I've found it useful. And it applies whether you're writing from scratch or adapting existing code. The cycle goes like this
- Pick the most important part.
- Make it run.
- Make it right.
- Go to step 1.
Don't overcomplicate things. Keep it as simple as possible, but no simpler. Whatever you do, don't ever
skimp on making it right. Code that isn't easy to understand is hard to extend. And the extended code will be even harder to extend. And the cruft will kill you.
There's another important step that I haven't put in there, 'Write tests'. Some say they should go before step 2, some say after. But not having them is a recipe for disaster. Every time you get a bug report, write a test that fails because of the bug; the process of doing this will often give you the information you need to make fixing it easy. And it's one more test.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||