A career in programming is not soley about technical acumen, although being good at coding is helpful.

Communication is almost a key in landing a good job. Being able to express what you mean in clear language that non-technical people can understand is vital!

Understanding and solving people's problems is also very important. Often a customer will ask you to do something, but they aren't telling you what they mean, only what they think you need to know. You need to be able to ask a lot of questions, even questions you might take for granted. If you can give a customer what he really wants then you're on your way to making it!

Lastly, I can say I am a Perl Developer, and have been contracting in this mode for the last year-and-a-half. Previous to that I was in a non-software-development role but had been creating systems in Perl for others as a natural part of improving processes in another company.

Perl roles are thin on the ground, this much is true. There isn't the prolific listing Perl roles as there is of C++ or dot-Net or Java. You need to be flexible about where you live.

Some companies have moved towards Perl-based development, and these companies cannot get enough good Perl programmers. Often I have been asked in a role if I know anyone else that is good - and I have to say no as I know few good Perl programmers personally.

Companies that look for Perl programmers rarely look for code-monkeys, like other language based roles may require. A company that moves towards a Perl environment often is looking for a pragmatic developer that is as valuable in design and creativity as they are technically.

Which brings me back to the start of this article. You must develop your communication and creative skills if you want to succeed in Perl development roles, by-and-large. Good luck!


In reply to Re: Market Stupid to Understand Perl by monarch
in thread Market Stupid to Understand Perl by pengwn

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.