As said by others, a good interesting homework question, be it from someone at school or at work, benefits other readers as well. A cheater won't get far in technical profession anyway (it's another story with other professions) and should the person a "cheater" actually learn something and apply the knowledge to do something useful in life, that's only a win-win situation for us. So, we might as well keep and even answer the good homework question for the sake of competent learners.

Besides, the responsibility of catching a cheater lays squarely on the teacher at school and the school system. At least, it should be obvious to catch some with great performance discrepancy between take-home assignment and in-class exam or any kind of in-person quiz.

(That reminded me a post a while ago that told an anecdote where a job interviewee claimed to be chromatic but failed to explain most of "his" own code, let alone the fact that many people do know who chromatic is.)


__________________
Update: I slipped my mind. Thanks blue_cowdawg for reminding me. I forgot how many phony consultants I've encountered and forgot some people don't actually have to do work for professional advancement, just cunningly claiming credit.

Update: The anecdote mentioned above came from Re: CPAN Authorhood

In reply to Re: Homework threads aren't necessarily evil by chunlou
in thread Homework threads aren't necessarily evil by dragonchild

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.