Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
    I guess my question is what I should do to take my knowledge of Perl to the next level.

One way to raise your expertise: expose yourself to different languages, see what they do well, learn their idioms, and apply that to Perl. Lisp is the best example I can think of: if you get into Lisp, you'll learn all kinds of cool tricks involving anonymous subs, closures, lists, function application, and functional programming. (You can get pretty much the same techniques out of Haskell, but you'll miss currying and you'll even get to keep currying when you switch back to Perl.) Most of these tricks can be done in Perl.

As a happy consequence, you'll also have a bigger toolchest of techniques to use. Some problems are hard with one tool, and trivial with another.

Another way, which works really well and shows results quickly, is to subject your code to relentless peer review. Having other people paw through your work, pointing out which bits are awkward, which are error-prone, which are hard to maintain, and sometimes which are elegant, is a tremendously valuable learning tool. If learning other languages expands your toolchest, code review sharpens the tools.

I can't emphasize enough how important code review is. I'd say the primary advantage to working on an existing Open Source project is that you'll be able to push your code on other experienced programmers for review.

As a happy consequence, you'll develop some extra humility.

Update: Clarified the Haskell/currying point: you'll miss Haskell's currying when you go back to Perl. (IIRC, Perl 6 will support curried functions, so maybe it's not so big a deal.)

Update 2: So you can get curried functions in Perl, albiet with a bit more trouble than in Haskell. Thanks, educated_foo!

Good luck.


In reply to Re: the next step by FoxtrotUniform
in thread the next step by emilford

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 exploiting the Monastery: (3)
    As of 2018-06-23 04:56 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (125 votes). Check out past polls.