So what you're suggesting is that the only difference between you and your friends is the language you use, and your salary?

First of all, money isn't everything at a job. There's also the reward for a job well done, the fun you get out of working with a bunch of really bright people, the chance to learn new technologies, a nice workplace and maybe a pleasant commute.

I moved from C, to awk, to Perl .. yes, there were some new things I had to learn, but I was able to get started fairly quickly. Am I still learning? You bet I am -- just today I made the connection betweem ?: and "Don't include this group in the collection of numbered results in the s command'.

But as a C programmer I knew about $foo = (condition) ? bar : baz; already, so that construct didn't throw me off.

Perl is actually an amalgam of C, shell, awk, sed, and (I'm told) some LISP as well. There may be other bits in there as well. Thus, moving from Perl to C would be fairly simple.

And don't concern yourself too much about what your employer thinks .. sometimes (gasp) they're actually *wrong*.

Continue to learn both. Why do you feel you need to specialize? I have experience with C (15 years), various flavours of assembler (several years), and Perl (5-6 years). I also know databases (dBase III, ingres, MySQL and PostreSQL), and a fair bit of HTML, CSS and JavaScript. And I continue to learn new stuff all the time. In this business, you have to continue to learn all the time.

Don't have a preconceived idea of what tool you want to use or what path you want to follow -- be more flexible and accept challenges as they come to you -- just remember, you have to keep learning, reading books, staying up to date on what's happening in the industry. Never stop learning.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds


In reply to Re: Is Perl a good career move? by talexb
in thread Is Perl a good career move? by Mutant

Title:
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, details, 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, summary, 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.