This sounds like a management strategy that is doomed to failure. How can you effectively manage something when you haven't taught the skills to your engineers (or hired them, or hired a tech lead) and then try to tell them that they are doing it right or wrong? I would look at yourselves first and tried to see if you have done a good job managing a situation, because right now it seems like you are managing in retrospect, which isn't good.

That being said, if everything is working, you could judge based on the survival of projects and whether or not certain projects have needed to be team projects or extended. If projects can be easily extended and worked on by multiple people, that's a really good sign for any language.

In reply to Re: Perl Test by Anonymous Monk
in thread Perl Test by Faoahy

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.