Re: RPG instruction

Actually, it should take the good and the bad student the same amount of time to
finish.

The Good student is going to get the lousy program handed to him, and take a
bit of time to get the modification to work.

The Bad student is going to get the well written program handed to him, and take
a bit of time trying to figure it out.

The only ones who will really suffer are the lousy students being handed a lousy
written program.

Regards,

Jim Langston

Scott.Lindstrom@zenith.com wrote:

> >Step 2: Have everyone in the class hand their program to the person on the
> >right (or left) and ring shift (last guy on row takes to first guy on
> row).
> >Step 3: Have everyone in the class make a non-trivial change to the
> program
> >just handed them.
>
> The problem I see with this (in an academic environment, where grades mean
> everything), is that a lousy student can receive the program written well
> by a good student, so he fares well. Then the good student receives a
> *really* lousy program to modify.
>
> Granted this is what happens in the real world, but when grades and GPA's
> are so important, it's a bit unfair to make the good student work ten times
> as hard as another student just because he received bad code.
>
> >Another way to implement your technique would be to give all the students
> >the same working program and have them modify it.  Stage one: give them
> >a "good" program to work with.  Stage two: give them a horrible one;
> >ideally
> >one that has already been badly maintained by a different programmer than
> >the original.
>
> This is much fairer.
>
> Scott Lindstrom
> Zenith Electronics

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---