I’ve read this response three times so far without completely understanding why you’d say that I “underestimate the problem” here, when you and I seem in fact to be saying the same thing.

If the project at-hand was originally and substantially developed in C++, then it is absolutely correct to say that a substantial body of experience in that language might be called-for in order to properly assuage the business risk that the person you just hired, in fact, does not know what he is doing and is too-green to know it.   (May I please have a quick count of how many heads are bobbing up and down right now, please?   Thank you.)   I rest my case.

The key word is that ... no matter what language(s) were used to develop the software, the project must have an assured service-life “for years.”   C++ is a great language .. so is Perl .. so is Python .. so is PHP .. so is .. well .. ;-) Java is out there, too ..   The multi-million dollar decision was made some time ago, and it was in fact not (or maybe it was? ...) a lousy decsion, but ... “We are here now, en-ter-tain us ...”

The people whom you call “easily hired” are not the ones you really want:   the people who have just one-or-two languages under their belt.   Monster.com will serve up people like that by the hundreds.   The people you really need are the ones who can truly set a programming-language tool in context.   And who can set a project in similar context, no matter what language(s) were used so-far in its construction.

Indeed, the people who can un-flinchingly approach a project that was done in a language they had never seen before, and who are not bluffing in their confidence, and do it because they have encountered so many technologies before.

In reply to Re^2: For thought: "Perl in the greater context of (me and) the software business by sundialsvc4
in thread For thought: "Perl in the greater context of (me and) the software business by sundialsvc4

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, 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, 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.