comment on

This does not bother me, as it is generally irrelevant. As you already passed the technical screen, so your tech side on Perl has been recgonized already, pointing out those little bugs does not give you more scores. Especially something like autovivification, is even not a bug, some people can choose to disregard the autovivification feature in Perl for style reasons.

If there is a situation prompts you to mention it during or after the interview, there is no harm to mention it, but don't mention those intentionally. If I am the interviewer, and sense that someone is too eager to show off just because of some really trival stuff, I would strongly doubt how deep the person is both in terms of tech and personality, and put him to the bottom of the queue.

In reply to Re: An Interview Quandry by pg
in thread An Interview Quandry by dws

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.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks