I also recommend The Pragmatic Programmer.
But another thing I recommend is, don't write pseudocode for Perl. In a low level language like C that is needed, but in a high level language it is less needed. I prefer another system of prototyping: the rough draft. Or, as the saying goes, (anybody know who I'm quoting?) "plan to throw one away. You will, anyways."
To clarify my position on design documents, while I don't think pseudocode is particularly valuable in Perl, I do think charts are valuable, and I do recommend using charts to determine the best data structures.
Snazzy tagline here
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||