Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Why restrict yourself, look at Perl AND Python, gaining familiarity with more than one tool set is not a bad thing.

While you are at it look at JavaScript and Node (or at least node.js).

Having serious exposure to multiple languages increases the number and variety of gigs you can tackle. It puts you in the position of letting the Problem Domain determine the Language -- time sensitive jobs in C; text handling in in Perl or Python; regular expressions in Perl; web-code in Perl, PHP, or AJAX (or node.js and the web-server of your choice). Increased flexibility reads as increased marketability.

In addition to increasing the chances of getting hired/assigned to interesting projects, there are cross-pollination effects -- the way that I look at designing a Perl code effects the way I look at writing Python tools for Ops Monitoring folk. Thinking about how Perl's CGI module works influences the code that I write in JavaScript (and conversely). You don't need to be a Super Star in the language, but you do need to be able to truthfully say (and demonstrate) that you are a Journeyman Programmer in whatever language the project needs.

While you are at it, don't restrict yourself to learning one or two other languages. I am currently working my way through node.js and JavaScript (again, after I read Doug Cockcroft's little book). When I have reached my comfort level there, it's time to go back to FORTRAN; my third kid is working on some interesting problems involving mapping software for the Forestry Service. All of the code is written in either FORTRAN or Python, and there are some interesting issues and problems there. (Think real-time maps of forest fires....)

I Go Back to Sleep, Now.


In reply to Re: I want you to convince me to learn Perl by Old_Gray_Bear
in thread I want you to convince me to learn Perl by kasxperanto

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 scrutinizing the Monastery: (6)
    As of 2018-06-22 23:27 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (124 votes). Check out past polls.