Peer reviews can often be filled with dread for the author. Especially if their peers are particularly critical of the material. It doesn't help if you've never had your work reviewed by a group of peers before, either.

I think it's a grand idea to have people review your code -- one to find errors (although that's not the objective here, as noted by the Update). But I think it's more important to be able to be comfortable in a peer review. If I make a mistake in my code, I want to be objective enough to be able to see it. That means not taking offense when someone points something out. For some people that comes naturally, for others it takes practice.

It's just the same as going to mock interviews. It's just the idea of getting used to 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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.