Academic Dishonesty

[Sir_Brass]

Then if it's unethical, I fail to see how it is NOT immoral. Ethics is based off of an accepted set of moral values. If it's unethical, then it's also immoral. Now, something can be ethical, but personally immoral to someone, and thus is would violate their own ethics.


Trust me, I'm an EE major, and in all my engineering classes I have a little something on ethics drilled into my head in each class. Ethics are a BIG issue for us engineers. Violating ethics is a GREAT way to kiss ANY hope of a career in engineering anywhere goodbye.

[graycie]

i can see the point of programming equations in a graphic calculator or borrowing someone elses homework, but like someone else said if you don't really do it your screwed for the exam.

in this particular incident i think the punk was waiting for the woman who sits next to me (who all ways reads her assignments) to hand hers in and then grabbed her quiz after she put it in the pile. i think she was in complete shock along with the 5 other people left in the class when he did that.

[-J�ker-]

Originally posted by Miscue


I can't remember what class it was, but they required the memory to be dumped out. So, I made a fake menu with a fake mem delete button. I wasn't about to lose the programs I wrote on it...

please explain how you did that

[lopxtc]

Now this is something I never had a problem with myself since very few people write original code anymore anyway ...

Where the real challenge comes into play is when the instructor wants comments in the code to describe why you did what you did ... thats where you find out who wrote their own code and who just borrowed it from someone else.

Aaron

Originally posted by Miscue
I used to pass around source code, cuz I was a cool guy. But blatant cheating like that, that's ridiculous. As far as homework goes, I don't see what the problem is because you just screw yourself if you don't have it together when the test comes around...

The A students are some of the best cheaters around...

[Kevmaster]

Graycie,

I personally would have waited for the sub teaher to come in there and have told her. But, yes, tell your teacher as soon as possible. I've always been brought up in an honest environment. Here in college, it is carrying over. Sure, some people copy homework and share some ideas in labs, but blatent copying on a test, I wouldn't stand for it. Call him out on it to the teacher

[cphilip]

Originally posted by hylen1
at our highschool, cheating is the only way to survive, everybody does it, most teachers will catch a bad cheater anyways, and smart cheaters are smart enough to not get caught. I cheat, who doesnt, but i know who is against it, like 3 people at our school, and they sit in the corner by themself. Cheating is a must. I am not gonna do 3 hours of hw a night. I see what class is most important and do that stuff for real, the others stuff i copy from someone at school.

Cheaters always say stuff like this. But yet its totaly wrong. Lamer. I'd rather fail than cheat. At least I still have my self respect and dignity. In the ends thats all anyone really has. You even lack that.

[LaW]

Originally posted by lopxtc
Now this is something I never had a problem with myself since very few people write original code anymore anyway ...

Where the real challenge comes into play is when the instructor wants comments in the code to describe why you did what you did ... thats where you find out who wrote their own code and who just borrowed it from someone else.

Aaron

Thats not true at my school, the submissions are ran through a program that checks for similarities within everyones code, if it matches someone elses by so much then you are called in to discuss your code with the department head. That is where you would have to explain your code, how it works and why you did it that way. If you cant do that you get an automatic fail of the class.

I have never been one to put detailed comments on why I did something a certain way.

[lopxtc]

I have heard of some places doing stuff like this, but to me it almost seems that it would take more time then it might be worth.

The local big name schools around me dont check source ... they are mainly concerned with does it run, and does it do what it is supposed to do. Heck the one Java teacher even points out places to go and look for solutions. He is also a firm supporter of Open Source and a big believer going into the community to find solutions to problems that you are having.

Given that very few people are individual programmers, I find that classes were students are grouped into development teams and assignments are done and graded as a group is a great way to demostrate real world development situations. Each student is still required to comment and explain their portion, but this is how is should be in real life anyway.

Aaron

Originally posted by LaW



Thats not true at my school, the submissions are ran through a program that checks for similarities within everyones code, if it matches someone elses by so much then you are called in to discuss your code with the department head. That is where you would have to explain your code, how it works and why you did it that way. If you cant do that you get an automatic fail of the class.

I have never been one to put detailed comments on why I did something a certain way.

[LaW]

Originally posted by lopxtc
I have heard of some places doing stuff like this, but to me it almost seems that it would take more time then it might be worth.

The local big name schools around me dont check source ... they are mainly concerned with does it run, and does it do what it is supposed to do. Heck the one Java teacher even points out places to go and look for solutions. He is also a firm supporter of Open Source and a big believer going into the community to find solutions to problems that you are having.

Given that very few people are individual programmers, I find that classes were students are grouped into development teams and assignments are done and graded as a group is a great way to demostrate real world development situations. Each student is still required to comment and explain their portion, but this is how is should be in real life anyway.

Aaron

I personally hate Java... I picked a school that did not teach it. I do know Java enough to program in it however. But honestly the time it takes to check the source is nothing at all. They have the programming assignments graded within a couple days.

Early on, how does it help you develop into a programming mentality if you are just going around copying code from everywhere when you are not going through the problem solving involved yourself? It lacks thought on your part and I think early on that has a negative affect.

I had a class last semester actually that had a few "group" projects and it was a lot more enjoyable.

[WickeDKlowN]

Who Cares? It isn't hurting you, and if they really do what you say, the're gonna fail anyway. Don't get them kicked out of the class, then they'll just have free time. Make them suffer...

[Kevmaster]

Originally posted by WickeDKlowN
Who Cares? It isn't hurting you, and if they really do what you say, the're gonna fail anyway. Don't get them kicked out of the class, then they'll just have free time. Make them suffer...

letting cheating go can always come back to bite you in the ***....

[grw4w34]

The only calss i cheat in is my religious studies class. God must hate me.

[Miscue]

Originally posted by lopxtc
Now this is something I never had a problem with myself since very few people write original code anymore anyway ...

Where the real challenge comes into play is when the instructor wants comments in the code to describe why you did what you did ... thats where you find out who wrote their own code and who just borrowed it from someone else.

Aaron

I've never copied anyone's code because I was interested in doing it myself. And most people's code sucks anyway, and I would not want to turn their stuff in.

[-Carnifex-]

Originally posted by Kevmaster


letting cheating go can always come back to bite you in the ***....

How so?

[Sir_Brass]

Originally posted by LaW

I have never been one to put detailed comments on why I did something a certain way.

Same here. My code is short, though, since what I write has to fit into a VERY limited memory space (the memory on a microprocessor), and certain functions are going to be written the exact same way for everyone, like serial interrupt code, timer interrupt code (depending on what the timer is used for, and usually it's pretty simple), and the serial transmition function code. But for the code that really matters, the BEEF of the code, I put in comments to explain WHAT I'm doing, not WHY I'm doing it, b/c WHY I'm doing it is usually quite obvious. If my professor can't follow my line of thinking, however, then it usually means that I've got some logical errors in the code.

Sometimes we share code ideas: as in, HOW to get something done, but not the CODE that it entails. After all, if you can be told fairly specifically what you need to do (as in what the micro needs to compute and then send out and at what speed, etc.) and still not know how to code that, then you have no business being in the class in the first place. Example to the code sharing: I was quite open in sharing with a classmate what integer TH0 and TL0 should get to produce a 50 micro-second timer interrupt rate. My professor heard me, and had no problems with it. After all, it was a minor detail that everyone would need. It did not affect the coding style of the other person.

it's mostly in your style. if you know what you're doing, you'll have your own unique style that will be clearly evident even if you were told how something should be coded. This is assuming you know how to code.

If you just rip code from someone else, then you ought to get written up, b/c if the professor sees two copies of code that are exactly the same, then he'll more than likely give 0's to both and have BOTH written up for plagerism, and that is something that can get you kicked out of this school, or at the least fail you in that class immediately. Do the person who did the original work a favor, and make sure that only the cheater is punished.