I think Seekers is quite different from what was proposed
for the code review section.
- Seekers:
- the code doesn't work; the poster is stuck.
Post the minimal example and describe errors.
- Code Review:
- the code works, but the poster wants to
know if there's a way to improve a function's
efficiency, or if there are some bugs in the
module that s/he hasn't seen, or if there's
a pitfall in the program s/he didn't notice.
That said, I think Review is more or less like Craft.
See the
description of the various sections. I get the
impression that snippets and catacombs could easily
be used for polished pieces of (snippets and standalone
programs respectively) code (polished modules belong at
CPAN of course). The code in these sections should be
good enough for someone to use. It might actually be
nice to have these sections moderated, allowing only
code that passed review to be found in these sections.
Craft, on the other hand, is a place
to show off code. If something's on display, it's going
to get comments and critique...at least that's how I see
it.
Update: Merlyn, I agree that it's good
to have it clear that people will critique. I just
think a new section would be redundant. If Craft is
what I think it is (and if not, what is it
for?), it would certainly benefit from a clearer
description, and possibly even from being renamed to
Review.
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.