Flustering/stressing out candidates in an interview is not
always a bad thing, though. I guess it mostly depends on
the job that you're interviewing for. If it's for a sys
admin or webmaster or programmer who will have to quickly
fix broken production systems, I'd want someone who can think
on their feet. I'm not a fan of finding out at a bad moment
that someone chokes up & can't hack together code when
they're stressed. So there's no point of unnecessarily
stressing out every interview candidate, but if it's useful
for making a hiring decision, I'm all for asking tough
questions that they might not know the answers to & getting
them a little stressed out. -- cat
-
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.
|