Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!mailrus!utah-gr!utah-cs!cs.utexas.edu!utastro!nather
From: nather@utastro.UUCP (Ed Nather)
Newsgroups: comp.edu
Subject: Re: looking for cheating detectors
Message-ID: <2927@utastro.UUCP>
Date: 23 Jul 88 15:11:34 GMT
References: <4513@medusa.cs.purdue.edu>
Organization: U. Texas, Astronomy, Austin, TX
Lines: 18

In article <4513@medusa.cs.purdue.edu>, narten@cs.purdue.EDU (Thomas Narten) writes:
> Moral of the story: it's relatively easy to catch cheaters; the hard
> part is figuring out what to do with them once they're in your office.

Indeed.  Try to explain to them that what they did -- take someone else's
debugged code and use it themselves -- is wrong.  It's what they'll do
when they grow up, and it isn't called "cheating."  It's called "smart
programming."

I think it's unprofessional to short-change the real education of your
students to make your teaching job easier.  But I recognize that this is a
minority opinion.

-- 
Ed Nather
Astronomy Dept, U of Texas @ Austin
{backbones}!{noao,ut-sally}!utastro!nather
nather@astro.as.utexas.edu