R. Clayton (rclayton@monmouth.edu)
Mon, 23 Oct 2000 14:47:48 -0400 (EDT)
I would feel a lot more comfortable working on the next project with your
code, but then again maybe not, I just want to make sure it's ok to do that.
Thanks.
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 your code and use them when I write my code?", the answer is "No,
you can't take notes and use them when you code."
If you have any doubts or questions, you should bring them to me and we can
work them out. However, if you do what I suggest above, then you should be in
good shape. If you're not sure, though, here's another test you can try: have
somebody point a random section of your code. You should be able to explain
what the code section does, how it does it, and why it does it. If you can do
that for any section of your code, you're almost certainly in good shape.
This archive was generated by hypermail 2.0b3 on Mon Dec 18 2000 - 13:30:05 EST