I'm a similar pickle, though my primary experience has been with Borland tools. This puts me into a slightly worse situation that you're in, especially given the depth of MS deployment/presence in my neck of the woods.

You're right; many job openings are for MS tools/technologies. However, I'd probably take that position because I think it will make you far more valuable than you are now. You'd be exposed to other ways to solve problems, be able to add more tools/skills to your kit, and gain practical experience with Perl/Unix.

In a short time, you should be able to combine both points of view into far superior solutions than those solely trained in a single methodology/tool set. In turn, this should let you compete for different types of positions, those requiring answers using the best of all worlds.

I would strive to keep your MS skills as sharp as possible, possibly by participating in relevant newsgroups or online communities in your spare time. To my mind, understanding multiple tools and philosophies makes you a better problem solver in the long run. This also gives you a backup plan. It's easier to take risks if you've got one in place.

Also, there's the happiness factor. To my mind, it's better to be happy than rich. Security can lead to complacency...and that can lead to obsolescence. Should the organization you're working for choose to make a paradigm shift, obsolescence leads to a pink slip.

I'm sure we all know people who hate their high paying jobs. In my book, if the job makes you happier, take it. I think you'll find yourself far more energized than limited. At the very least, you'll have enjoyed yourself, regardless of what the future brings.

As far as the future goes, MS will continue to look for ways to "innovate" and grow their business, as will other vendors. We will continue to see new ways of solving problems. I believe, though, that you can adapt to whatever tools are available if you have mastered the basic skills required for related tools.

My two cents; as always, your mileage may vary.

--f

In reply to Re: A career dilemma by footpad
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.