🚀 go-pugleaf

In article <ct9g_2m@rpi.edu> night@acm.rpi.edu writes:
>contest itself is divided into 2 parts.  The first part, each team
>works on getting a minimally functional system running.  At the
>end of the first part, the programs are all submitted and copies
>are made for each team.  Each team then has say, a half hour to
>sort through the programs and choose one (which can't be their own)
>program which they will then try to add as many features as they can 

Sounds like a good idea, but I think there is a trap here.  In particular,
there is a disincentive to making the initial program easy to modify,
easy to understand, etc.  I would seriously consider having solutions
done up beforehand: just one or a selection using different approaches/styles,
so that the playing field is level for round two and there is no temptation
to booby-trap one's submission for round one.

-- 
Steve Nuchia	      South Coast Computing Services      (713) 964-2462
	"Innocence is a splendid thing, only it has the misfortune
	 not to keep very well and to be easily misled."
	    --- Immanuel Kant,  Groundwork of the Metaphysic of Morals
-- 
Steve Nuchia	      South Coast Computing Services      (713) 964-2462
	"Innocence is a splendid thing, only it has the misfortune
	 not to keep very well and to be easily misled."
	    --- Immanuel Kant,  Groundwork of the Metaphysic of Morals