Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others admiring the Monastery: (3)
As of 2024-04-19 19:32 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found