I'm not following your point here. Are you suggesting that someone has forfeit their right to learn something new N hours before an interview or test? If so, how many hours 12? 24? a week?

At my university, homework and even exams were designed to teach. The learning happened while we were working on the problem sets and exams, not "long before". We were in fact encouraged to discuss concepts, approaches and ideas with one another as we prepared our work.

Though I am not a professional teacher, I have spend countless hours successfully tutoring people that others told me had no chance. They were too dumb. Or didn't try enough on their own. Or it was too late. Or they were too much effort. In reality, they never believed in themselves or were intimidated by something that seemed easy to everyone else. When someone came along with the attitude - "you can learn", they flowered. So I don't believe in "deserve to fail". I do believe in "you will inevitably fail this time because there is too much to learn for now, but next time can be different and here is how we can make it so..."

If someone doesn't have enough knowledge to pass an interview coming up within hours, they aren't going to miraculously get it by reading a few answers at Perl Monks, especially if those answers focus on explaining the core concepts and language elements needed to solve the problem rather than hand out a solution to a particular problem on a platter. Most likely, that job opportunity will be lost to them. But helping them get the job isn't the point anyway.

Those of us who answer questions like these and care about learning, do so because we are thinking about the person's development as a whole. We want to communicate an excitement about Perl and programming and the kind of thinking needed to succeed in it. The job interview or test may be tomorrow, but the learning process will go on afterwards for many years if we can communicate and infect others with our enthusiasm.

How many of us in life start out doing something for the wrong reasons and end up getting hooked for the right reasons? Does it really matter that someone came to PM looking for a shortcut, if they get snookered into actually learning something because someone took their silly and overly narrow question seriously and looked behind it to find something useful to teach?

Best, beth

In reply to Re^3: Stop with the interview questions already by ELISHEVA
in thread Stop with the interview questions already by ssandv

Title:
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, details, 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, summary, 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.