🚀 go-pugleaf

In article <GLENN.91May2094528@curie.ces.cwru.edu> glenn@curie.ces.cwru.edu (Glenn Crocker) writes:
>hurwitz@ENUXHA.EAS.ASU.EDU (Roger A. Hurwitz) writes:
>
>   It may not be as much fun, but why not make
>   these things software design contests, and judge the contestants on the
>   quality of their designs?  Or change the format to give contestants more
>   time and judge the implementations on the famous "ilities".
>
[ some cute comments deleted ]
>
>Seriously, how would you have these contests judged?  Have the judges
>each take an enormous amount of time to thoroughly read and understand
>each team's entries, then have them vote on the winner?  The current
>contests take quite a bit of time to judge, so you'd have to decrease
>the number of problems.  My point is not that you're wrong, just that
>what you want may not be possible at a contest with 100+ teams....
>
At the finals of the ACM Programming Contest, the results aren't announced
until the following day.  That should be enough time to judge on whatever
grounds are desired.  The real problem is that it is much easier to use the
objective (does it produce the correct output) judging procedure than the
subjective (would a good programmer have organized this code this way).
-- 
Blair A. Seidler          Teaching Assistant, Department of Computer Science
(212) 853-6874                           Columbia University
   "Columbia University School of Engineering and Applied Science does not
     even know that my opinions exist, and would ignore them if it did."