Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
A few thoughts...

Reading and studying only helps to a point. I find fixing, adapting, and building things is a better way for me to expand skills. This improves both developer skills and Perl skills.

Developer skills involve computer science, work habits, planning techniques, and more. Much of this is learned more easily from others than from books.

Perl skills tend to involve specific tasks like file processing, hash manipulation, and data base interation. I find that even when one thinks they know a language well, there tends to always be something else to learn.


In reply to Re: Learning the Deeper Secrets of Perl by bwelch
in thread Learning the Deeper Secrets of Perl by radiantmatrix

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.