Breadth can be good. And unless your market is different from Silicon Valley, being as much as a year out of date on a particular stable technology isn't that big of a negative. (Being out of date on an unstable technology is kind of iffy, and things in Microsoft land look to be getting unstable again as people sort out .NET.)

Something to ask yourself is whether you want to compete in the market based on your tool skills or based on your problem-solving skills. Problem-solving skills have a longer half-life than tools skills, and tend to get you placed higher in projects. When tapping architects for a project, I look to thinking ability and exposure before looking at narrow technical skills.

If you do decide to market yourself based on tool skills, there's some benefit to having a rare skill, as long as there's at least some market for it. Plenty of people know C, fewer know Perl. Fewer still know how to speak Perl, SQL, and HTML. That's a skill set that I'd bet on, were I going strictly technical. Databases are hardly going away, and HTML will be with us for a while. Perl is a great way to tie the two together.

In reply to Re: A career dilemma by dws
in thread A career dilemma by ChilliHead

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.