Discussion of homework rule


 
Thread Tools Search this Thread
Contact Us Post Here to Contact Site Administrators and Moderators Discussion of homework rule
# 1  
Old 09-12-2003
Quote:
Originally posted by Perderabo
KLL, please click on the rules link at the bottom of the page and read our rules. Notice what rule 6 says about classwork.

This looks like a homework assignment. If it's not, just do this:

du -sk /some/directory
Geez .... the person can't even ask for some help debugging code that they have ALREADY written ? I don't see what's the problem with helping somebody who is obviously making an attempt to do the work. It's not like they asked to be given the code.
# 2  
Old 09-12-2003
not a fish on a plate

" Geez .... the person can't even ask for some help debugging code that they have ALREADY written ? I don't see what's the problem with helping somebody who is obviously making an attempt to do the work. It's not like they asked to be given the code."

.. and, unless it were trivial, neither would we give him the code solution.

'Give a man a fish and you feed him for a day, teach a man to fish and you feed him for life'

If KLL discovers the joys of D.Knuths 'Algorithms and Datastructures' becuse of his post, and then goes on to turn the psudocode to real bash scrips ...then my job is done.
# 3  
Old 09-12-2003
These posts were originally in this thread.

kowrip, Neo makes the rules. I don't agree with all of his rules either. But this one is on the money.

I have taught quite a few programming classes and I tell you that it crucial that I keep myself apprised of exactly what each student is capable of. I never give a student an assignment unless I am sure that the student can handle it. If I'm wrong, I need to know that. If I'm mislead, I will move ahead, leaving the student further behind.

What's more, the ability to locate bugs is one of the most valuable skills that a programmer can possess. If we point out bugs in a student's code, the student will never develop that skill. There are quite a few programmers who never make it there. These forums are full of them. Debugging skills are a separate fish that the student must learn to catch. You are ensuring that debugging is a fish that the student will never know how to catch. That is the harm that you find to be so very invisible.
# 4  
Old 09-13-2003
Quote:
Originally posted by Perderabo
These posts were originally in this thread.

kowrip, Neo makes the rules. I don't agree with all of his rules either. But this one is on the money.

I have taught quite a few programming classes and I tell you that it crucial that I keep myself apprised of exactly what each student is capable of. I never give a student an assignment unless I am sure that the student can handle it. If I'm wrong, I need to know that. If I'm mislead, I will move ahead, leaving the student further behind.

What's more, the ability to locate bugs is one of the most valuable skills that a programmer can possess. If we point out bugs in a student's code, the student will never develop that skill. There are quite a few programmers who never make it there. These forums are full of them. Debugging skills are a separate fish that the student must learn to catch. You are ensuring that debugging is a fish that the student will never know how to catch. That is the harm that you find to be so very invisible.
In my academic experience, professors taught the concepts and very rarely got into the guts of the code. Learning the actual syntax and pitfalls of the specific programming code was the students' duty. Being that I didn't have much guidance in this area, I found it very helpful for somebody to point out an obvious problem in my code. As long as I understood what the mistake was, it was very beneficial to me.
# 5  
Old 09-13-2003
Quote:
What's more, the ability to locate bugs is one of the most valuable skills that a programmer can possess. If we point out bugs in a student's code, the student will never develop that skill. There are quite a few programmers who never make it there. These forums are full of them. Debugging skills are a separate fish that the student must learn to catch. You are ensuring that debugging is a fish that the student will never know how to catch. That is the harm that you find to be so very invisible.
I've also NEVER seen any professor give any sort of lecture or even GUIDANCE on debugging code. If it's such a valuable skill, it should be emphasized more.
# 6  
Old 09-14-2003
kowrip,

The rules are the rules and they are not going to change (about homework problems).

Thanks.

Neo
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. What is on Your Mind?

Discussion culture

I want to start a small thread about discussion culture. From the past experience in different fora, I have little hope that any will come out of it. But I'll try it anyway, hoping to contributing to an improvement on the topic. I do not want to discuss a specific technical question, but only... (5 Replies)
Discussion started by: stomp
5 Replies

2. Post Here to Contact Site Administrators and Moderators

vb 3.0 Upgrade Discussion

Please discuss vB 3.0 upgrade or ask questions here. Neo (27 Replies)
Discussion started by: Neo
27 Replies
Login or Register to Ask a Question