in reply to Re: Technical Interview
in thread Technical Interview

With such open-ended questions, don't count as wrong answers which aren't exactly what you're looking for.

What techniques do you use for security in your CGI scripts?
Common sense simplicity and tightly control user input's affect on data and the system. (You were looking for Taint and CGI.pm weren't you? Sorry, they're not the be-all and end-all of CGI security. CGI.pm doesn't replace #1 and Taint doesn't fufill #2.)
When reviewing someone else's code what do you look for?
 Reviewing someone else's code for what? Style? Conformity to customer's standards? Security? Speed? Memory?
What are 2 necessities for all perl development code?
 Documentation and consistancy. (What? You were expecting warnings and stricture? Warnings and stricture are both encouraged by the standards here but not necessary in all cases...)

Replies are listed 'Best First'.
Re: Re: Re: Technical Interview
by grep (Monsignor) on Dec 28, 2001 at 00:05 UTC
    Ahh.. the point is to leave them open ended, at least with the first 2. It not only sees how some one thinks on their feet but, I can hear if they have a passion (or lack of passion) about security or good style. People feel free to go into stories. You don't get this with a "So you have HoA how do you extract the 5th element of 'foo'".
    I do not count "wrong" answers against people (unless they are just plain wrong. i.e. all you need is SbyO solutions).
    The warnings and strict question, I personally think is a leading question. IMO, as I interviewed perlers it really did help pick out the better programmers. The programmers that had passionate responses to the other questions almost always got warnings and strict right off the bat. They also elaborated on other things they think were important.

    grep 
    grep> cd pub 
grep> more beer
[reply]

In Section Seekers of Perl Wisdom