Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
    Translating it to something here, I would add a new section "articles", with general topics (eg "network sockets programming", "threaded processes") offered up for suggestion, and any monk wishing to write an article may do so. The topic suggestions should be limited to only higher level monks (6th or above?) to avoid having topic pollution ala Q&A/SoPW duplication. "Articles" can be as fundamental as a tutorial, or robust as pure example code with commenting, but it ought to end up being a combination of prose and code so that a message on how to improve ones programming is taught. Which means the message shouldn't be spoonfeed, but nor should it be so vague as "simply read the POD for everything you need".

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:

    <purl> quiz ? [ sound of cheers from #perl crowd ] <purl> quiz --> <purl> BEGIN{ local $@; my $f = 0; 2/$f } print "Done" <purl> bug or feature ?
(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:

    I hope abigail doesnt mind the repost...

    Date: Thu, 29 Mar 2001 20:40:16 +0200 From: abigail@foad.org To: fwp@technofile.org Subject: [FWP] So, you think you know Perl? Your exercise for today: 1) Predict what echo "" | perl -ple 'print q' does. 2) Run the above command and compare it with your prediction. 3) Explain any differences. Abigail

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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (4)
As of 2024-04-25 09:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found