R. Clayton (rclayton@monmouth.edu)
Sun, 2 Jul 2000 19:38:39 -0400 (EDT)
I wonder whether it's appropriate for me to refer to some of structures in
your implementation of readmbox.
Yes, that's why I made it available. I believe that one of the ways good
programmers get better is by reading other people's code to learn new ways of
thinking about and solving problems.
On the other hand, cutting and pasting, while good for improving hand-eye
coordination, is not a good way to learn. And there's the always-vexing
question of cheating (as I've defined it).
To avoid trouble, or to easily handle trouble if it arises, I recommend you do
the following: read and study my, or anybody else's, code in a room away from
the terminal. When you're done studying, put everything away and walk - empty
handed - to the terminal and start coding. If you get stuck, go back to your
study room and review the things you've forgotten or don't understand.
This sounds like a pain and I suppose it is, to some extent. However it has
two great advantages: you will learn enough about things to be able to use them
cold, and it will provide reasonable protection against cheating charges
because the things you use will be coded up by your own hands.
(And if, at this point, you have to ask the question "But, can I take notes
when I study and use them when I code?", the answer is "No, you can't take
notes and use them when you code.")
This archive was generated by hypermail 2.0b3 on Fri Aug 11 2000 - 15:25:05 EDT