Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

Great article. This post got me thinking a bit about how we operate here at Perl Monks. Some would consider this post OT, although not many, judging by its reputation. It would, on the other hand, probably be a "bad thing" if comp theory were to dominate the discussion, since this is a site about Perl. Nonetheless, it is very useful to look at the big picture when Perl Monking.

Relatively often, a new Perl programmer asks a question about a piece of code that suffers from a serious lack of computational understanding. The typical result is that we correct the poster's error, and she learns that doing what she did was not one of the right ways to do it. But we correct the person by saying, "how about this" or "I'd do it like this" or "Why not this way" and then posting code. The poster may have learned something, but she probably hasn't gotten the big picture.

When someone asks a question that is purely Perl, we should answer in Perl; but when someone is missing a point that holds true in all languages (perhaps space or time mismanagement) we should take a moment to fill them in on the theoretical considerations, if only minimally, and provide some references for further study. Not that I'm necessarily planning to take the trouble to do this every time a post like this comes up, but I should. If everyone does it from time to time, we'll encourage people to become better programmers and help Perl by making Perl coders more skilled. Just my little rant.


In reply to Re: MOPT-01 - assumptions and spaces by dbp
in thread MOPT-01 - assumptions and spaces by mstone

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, 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
  • 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others meditating upon the Monastery: (4)
    As of 2018-06-18 12:02 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (109 votes). Check out past polls.