From a learner's point of view, good code has a lot to do with intuition. It is not true that all good code is understood intuitively. This is due to the necessity of knowing a bit about idomatic Perl and allowing your intuitions to develop before you can really understand someone else's code. Of course, it also helps to know how that person thinks ;)
Unfortunately, the average learner doesn't know enough to have developed good intuition, so comments have to play a role somewhere. Perl can appear to be cryptic because of the shortcuts (e.g. syntactic sugar) that have been built into the language. And then there's the tendency to solve all problems with regular expressions...
So for me, good code is code that is clear once you read it (two or three times) and that has explanations for the stuff that is not so clear.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||