Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Here's an idea I've thought about for awhile, but never tried -- in fact I never tried to set it up -- but from your description, you might have the raw materials for it (if it seems worthwhile):

Present a bit of the old goofy code that is (mostly) self-contained -- maybe add comments about global variables to explain what they contain, if necessary. Then also present the equivalent chunk of logic as written in your current "non-icky" style. It might be instructive if the old version contains a flaw of some sort that is fixed in the new version.

The task is to determine whether the two pieces of code really do the same thing, and in the process of discussing the snippets, get a feel for which of the styles seems more familiar to the applicant -- and which one is easier for him/her to understand (might not be the same as the more familiar one).

As others have said, the key is still in the discussion more than in the "factual" answers. If the newer, better style confuses an applicant, but they really do get the older style, this might not be a bad thing, especially if they show signs of catching on to the newer one. You just have to figure out how much training you're willing to invest in "re-education", given that they have a leg up on the older coding style.

On the other hand, if the newer code is a walk in the park for them, but they can't work out how the old code relates to it, they might not be as valuable when it comes to doing maintenance and retooling on the old code base, and now you have to figure out how much time you want to invest in just ditching the old code and re-creating an app from first principles (not quite "from scratch", but almost).

In reply to Re: How to measure Perl skills? by graff
in thread How to measure Perl skills? by optimist

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 all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others chilling in the Monastery: (9)
    As of 2018-06-25 14:56 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (127 votes). Check out past polls.