As madbombx said, one of the reasons I really like PM is because answer the questions of others (something I still haven't done too much of) really forces me to know the answer myself, and not just in a wishy-washy hand-wavy kind of way.
I'm quite new to Perl Monks as well. I started coding Perl almost exactly 2 years ago when I was hired fresh out of school as an intern in an all-Perl shop. i had heard of PM before, but when I visited on my first tour through the language (reading the Llama and the Camel) it seemed way over my head. After 2 years of working professionally with a group of talented Perl programmers, I'm pleased that I'm able to grok most of the stuff that goes on hear, and even chip in an answer or node of my own now and then. Of course, there are still some areas that elude me - having learned Perl in a structured environment with coding standards, my JAPH- and golf-foo are quite poor.
I'm only now starting to really try to extend my Perl beyond that which I do at work, so I'm trying to dive more into XS, pack and unpack, and various other corners of the language. Perl Monks is definitely helping me with my goal of becoming not only a better Perl programmer, but a better programmer in general.
-
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.
|
