This is a very difficult question. About the best you could hope for is to weed out the totally inept, and hope whoever's left is reasonably competent.
The problem (IMNSHO) is that there hasn't yet been developed a consistent measure of code quality. Is it better for someone to crank out lots of workable code, or to write a few terse lines that get the job done? We might be tempted to choose the terse programmer, but perhaps the verbose one included code to check for inappropriate input; or (s)he wrote code that would be much easier to understand, debug, and maintain. What objective test could you use to decide a question such as this?
As I see it, fluency in Perl is only part of the question. Another part is the ability to develop appropriate, efficient algorithms. Without this, the fluency will be wasted. They will express their unclear thinking in fine Perl idiom.
-
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.
|