🚀 go-pugleaf

hurwitz@ENUXHA.EAS.ASU.EDU (Roger A. Hurwitz) writes:

   ...  There
   is no problem with quantity.  

This is arguable, but I'll leave that for another day.  I do agree that
there are problems with quality.

   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".

This is an excellent idea.  Please put together an objective non-language-
specific set of criterion for judging the quality of a program.  Hmmmmm.
Let's see.  Here's a first draft:

1.  Number of subprograms.  (functions, procedures, whatever)
2.  Length of variable names.
3.  Comment / Code ratio.
4.  ...
....

:-)

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....

   crisi
--
Glenn Crocker                   |  Your milage may vary.
glenn@ces.cwru.edu              |  Light bar not for occupant protection.
CWRU, Cleveland, OH             |  Don't drive on frozen lakes.
W (216)368-6133 H (216)754-1314 |  Do not taunt Happy Fun Ball.