Personally I'm sure that the most important thing is your knowledge and skills - even if you learned everything you know in your free time, at home - just becouse you like it.

Once I've beed working as an advisor - the company just wnated to know who (i think) woulf fit the best. Well - nobody asked anybody about any certificates, etc. There was one guy, who thought that he would be somebody special becouse of his RedHat Admninistrator Certificate or something like this. In fact, his application landed in the waste bin immediatelly he left the room. Why?!
He had a certificate, but had nothing to show. When he answered our questions he never got to the point... That's all. The first approach is that you have a certificate and they assume you know what to do. The second is that you have a certificate and work as you were told to - no evolution, just a learned template. Which one is better - it depends...

Personally I've never tried to find a job as a programmer, becouse I know, that there are people, who know Perl (for example) much better than me - so I just keep tring to improve my skills and have some fun :-)

Good luck!
Greetz, Tom.

In reply to Re: Suggested skill set for aspiring perl programmer? by tmiklas
in thread Suggested skill set for aspiring perl programmer? by DigitalKitty

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.