Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Ultimately, we’re starting to get the feeling that most qualified Perl developers in the greater Seattle area are already happily employed

Of course they are. Good developers are in demand and are rarely out of work (at least once they have some experience on their resumes). You need to make a case in your job listings and interviews that your company is a better place to work than wherever they are now, so that people who are not entirely satisfied with their current job will come to you.

I sympathize about not being able to find a lot of good people, but really, there are just not that many good people. I saw the same thing when I worked in a Java shop -- many candidates were really just getting by and hadn't given much thought to the pros and cons of the tools and techniques they were using.

I personally prefer to see code samples rather than give a test. I want to see what style of code people will use when working on real problems, including how they leverage CPAN and how they document things. I find that the usual concern of "Is it really his code?" is not an issue if you spend 10 minutes asking the candidate to walk through his code and explain his choices.

In reply to Re: Developer::Perl::Find by perrin
in thread Developer::Perl::Find by gryphon

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.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others lurking in the Monastery: (4)
    As of 2018-08-16 00:06 GMT
    Find Nodes?
      Voting Booth?
      Asked to put a square peg in a round hole, I would:

      Results (165 votes). Check out past polls.