The best thing to do is sit down and read a lot
reviews. I was too ambiguous about code ... book
reviews do not need to include code, but i think that
module reviews benefit from good, easy to digest, cohesive
code. There really are no rules for writing reviews for the
Monastery, that's why i recommend that you read a lot of
them and decide for yourself. As a bonus, you will learn
a lot more than you probably ever wanted to know about
Perl. ;) If you would like some recommendations, then check
's review of Data Munging
's review of the mod_perl Cookbook
even managed to get away with a
review on a Java book
And as always, when in doubt, post your review to your
scratch pad and politely ask the monks
hanging around the Chatterbox to critique it.
(the triplet paradiddle with high-hat)
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||