Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
My first response to your post as a lifelong antisocial non-joiner of things was unthinking disagreement, until I thought for a minute about my progress in Perl.

I had been using Perl for a couple of years before contributing to CPAN and then ending up a regular here, and I think my Perl (and programming knowledge generally) has shifted into a new (and much higher) gear since I started engaging with the community. Plus of course I now have a better idea of just how much more there is to know.

Engaging with the community is the difference between a programmer who blindly relies on the tools provided in the form of published modules, and hence works always within external constraints; and one who really knows that, if they find a bug or shortcoming in a CPAN module, they can fix it themselves. Put in vaguer but more general terms, the horizons of a community connected perl programmer are probably broader.

As an added bonus, it's probably fair to say that a perl-er who engages with the community is more likely to have a more realistic assessment of their own skill level than one who doesn't.

I'm not sure it's entirely true to say that one can't be 'into' Perl without engaging with the community, in the sense of being an enthusiast for the language, but it seems likely that one could reasonably expect higher standards from someone who does.

To address cogs point, sometimes it seems that monks make too much of the correct capitalisation of perl/Perl/PERL. Personally, I often miss out the initial capital when posting because I'm so used to typing:



"If there is such a phenomenon as absolute evil, it consists in treating another human being as a thing."

John Brunner, "The Shockwave Rider".

In reply to Re^2: People who write perl, Perl and PERL by g0n
in thread People who write perl, Perl and PERL by cog

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 musing on the Monastery: (6)
    As of 2018-07-21 02:14 GMT
    Find Nodes?
      Voting Booth?
      It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?

      Results (443 votes). Check out past polls.