The following pretty much sums up my
aesthetic taste in Perl code, so stick a coefficient of
.000001 on it and put it in the Joe Q. Perlhacker summation.
-
Rule #1a
-
A poem is not a good Perl poem if it would be
better without the Perl (i.e., if there is a better
non-Perl poem trapped inside trying to get out).
-
Rule #1b
-
Obfuscated code is not good obfuscated code if it
is just a program with the characters shoved around to make
ASCII art.
-
Rule #2
-
If it provokes an emotional response (other than
disgust) and #1 doesn't apply, it's worth posting.
-
Rule #3
-
If it provides an "Aha!" moment, it's worth
posting.
If the art of Perl poetry can be compared to conventional
poetry, then the art of obfuscated code can be compared to
mathematical problem posing. It's easy to create code that
is laborious to read, but it's hard to create code that
rewards the effort of understanding it.
Alakaboo: Don't get frustrated. Perhaps you should
emulate the habits of "real" poets, as related to me by
a poet friend of mine.
Poets write lots of poems. Many poems get
scrapped before they are finished, because they were bad
ideas in the first place or the poet just got stuck.
Poets rework their best poems, show them around, get
feedback and perhaps do more reworking, and then pick a
very few to publish openly. Of course, it's better to get
dissed than to be too shy.
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.