Yeah, but as I see that is not the only problem. As I see it you are trying to reach perfection immediatly. The trick here narrow the scope a little and what is the absolute requirements for success and what requirements are for perfection. You are looking into this problem with "We need to do this fast, there should be no bugs and it should also be easy to make faster(or keep performance) by adding X! oooh did I mention that it should be easy to maintain? Because bugs will occur, it does not always work faster(or keep performance) when you add X and we should also be ready to add feature Y within the deadline because we missed it when we started."

IMHO you need to focus on people that can produce maintainable code first, because out of that the individiuals in the team can derive high-quality and scalable code.

Also you can't do anything about the quality of the code if you don't know where quality lacks and you can't do anything to the scalability and performance of the code if you don't know where these issues are. And you'll have no chance of fixing them if the maintainability of the code lacks.

In reply to Re^2: Hiring Perl Talent, Hiring Perl Monks by JanneVee
in thread Hiring Perl Talent, Hiring Perl Monks by hacker

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.