Path: utzoo!attcan!uunet!ndsuvax!ncgus
From: ncgus@ndsuvax.UUCP (Jim Gustafson)
Newsgroups: comp.edu
Subject: Re: looking for cheating detectors
Message-ID: <1057@ndsuvax.UUCP>
Date: 27 Jul 88 10:17:50 GMT
Organization: North Dakota State University  Fargo, ND
Lines: 25


>In article <1405@devsys.oakhill.UUCP> steve@oakhill.UUCP (steve) writes:
>Ed Nather does have a point that most real programmers lift their code
>from other sources.  But there is a difference.  When I (or any other
>programmer) lift code, I make sure I understand the code I am working
>on.  Quite often I have to resturcture or debug something subtle that
					   ^^^^^^^^^^^^^^^
	[ more on why one needs to understand, not cheat ]

A THOT FROM THE PRAIRIE:
The only way to learn the art and craft of debugging is by doing it.
It's gotta be one of the most difficult skills to acquire.  Through
lack of practice, a student who cheats usually fails to learn how to
quickly debug, port, etc.

So the next time someone suggests academic cheaters should be treated
in some 'real-world' sense, consider how much *real-world* time is
spent testing and debugging code.

You've got to practice the piano to play it well.
-- 
--
Jim Gustafson			UUCP:     uunet!ndsuvax!ncgus    
North Dakota State University 	Bitnet:	  ncgus@ndsuvax
Fargo, North Dakota 58105	Internet: ncgus@plains.nodak.edu