I really like this idea. Additionally, I like converter's idea of a Perl Puzzlers book. On dalnet #perl, we have a wonderful user (who I do not think frequents this site) named PerlCure. He does something I have yet to see anywhere else: He makes quizzes for the above-average-but-not-stellar perlmongers present. For example:

(original credit for the quiz apparently goes to bline)

This sort of thing is interesting, but we could also, like Masem pointed out, have actual articles attached to this. I get something akin to this on the fun-with-perl list at least twice a week. We get golf, but we also get very interesting and informative questions such as:

Folks, these are the kinds of things that get me excited about perl, and make me interested in a new function I dont use or underuse, or use in a different way. I get a ton of innovation out of just little things like that. But we dont really see these too often on PM except for in ob-fu. Which is fun... but useless in terms of my really growing as a programmer. Well, almost useless.

Masem is right. Articles are a great idea. I dont think I'm qualified to make an article, though I'm happy to try. Perhaps we could have a Quest first to see what articles are wanted, and then, as Masem suggested, have articles submitted. Gee, that almost makes us a periodical. (This particular reason is why I subscribed to <sniff> TPJ)

One other note here, tilly suggested I go have a look at Dominus' website, which is excellent. I suggest that for anyone interested in learning more about perl.

I am still very interested in seeing what people have to say about this thread, and I'm glad to see what people have had to say thus far. I think the response is mostly uniform. People would like to see more intermediate-upper level content, as a lot of us have moved past the beginning and even intermediate levels of perl programming and are looking to transcend just hackerdom.

yours as always,
brother dep.

--
Laziness, Impatience, Hubris, and Generosity.

In reply to Re: Re: Summing up recent ideas into a concept: Code vs. Prose by deprecated
in thread Summing up recent ideas into a concept: Code vs. Prose by deprecated

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &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.