comment on

Ask, "what are some good books on programming that you've read?".

You want to ensure the programmer is not just a 'perl' person. Ensure that they have an appreciation for the art of programming. Often interviewers talk about the SDLC (Software Development Life Cycle). It's a buzzy keyword that is largely baloney, but essentially it means "have you written something, debugged it, debugged it some more, debugged it even more, and had to recode it cause the customer wanted something different?".

A good programmer learns. And has the experience to know how to code defensively, almost predicting what bugs he's likely to produce.

A good programmer is open to criticism of his source; every workplace has different styles, and fitting into a workplace with a different coding style shows flexibility and willingness to co-work with your group.

In reply to Re: Have you netted a Perl Monk or Perl Pretender in 5 minutes or less? by monarch
in thread Have you netted a Perl Monk or Perl Pretender in 5 minutes or less? by Anonymous Monk

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.


There's more than one way to do things
	PerlMonks