This is your problem right here. There is no rational argument for grading people on a class curve. That just makes the class a lottery and incentivises sabotaging for others to get an upper hand yourself.
This is your problem right here. There is no rational argument for grading people on a class curve. That just makes the class a lottery and incentivises sabotaging for others to get an upper hand yourself.
I did an exchange year, and sent my grades over to a professor. Guy was like "What's up with all the non As" and I had to talk about how we do things differently here (giving points for right answers, and then adding them all up).
Of course there's always an overall curving happening on a high level because teachers choose how hard to make assignments or not, and ultimately grades are not really fundamentally important, but when people just have those to judge you on and choose to, it really fucks things up.
but also the prof will know if the class is full of overachievers and curve in a way commensurate to the class
I don't think that people would typically go to the lengths of trying to sabotage someone else, in practice it could just look like a bunch of people working separately and not cooperating at all
In an ideal world, there wouldn't be any curves and the coursework would be tailored sufficiently for every cohort of students for every semester
But I admit I might be a bit radical here compared to most people. (Who I am sure will argue that utilising teacher time to the maximum is the only reason to gather students in one room.)
In the class I mentioned above, the prof and TAs weren't pissed off about people using each other to understand concepts or even high level design. They were pissed because people were copying source code verbatim, comments and custom debug messages and all
On a related note, if someone ever asked me for help with a concept or high level design I would be more than happy to oblige. But (most of the time) people aren't asking for that, they want source code that they didn't contribute to
this could be fixed by making assignments collaborative, but then the professor has no means of verifying where everyone is in terms of understanding
Those exams were often the most edifying couple hours of the whole semester. You also got a clear sense of the difference between you and a real master of the material which is a helpful lesson in humility.
I went back to grad school recently and it seems like that mode of testing has gone out of style in the last ten years. The exams I took were geared more towards establishing a minimum bar of competence, more for my future employers' benefit than my own.
I think the problem with this is, although cool, very few professors are capable of doing this well and very few students benefit from it. IOW, it doesn't scale.
To my mind, oral finals or 'discussions" would repair the cheating issues quite well. But again, it's hard to scale and professors would need to be trained in how to do them.
When I set (free-form written, math/CS) exams, I always made a point of designing the exam in a way where I didn't really expect anybody to get more than 90% of the points. I also made sure that students knew this.
I always set grade brackets before grading (e.g., 80% of points gets you an A, below 35% is a failing grade, and so on). I always ended up with a pretty reasonable grade distribution.
It was simple. The weekly assignments contained 6 questions. One of those was the mindfuck question and wasn’t graded (if you solved it you got extra credit, but hadn’t been solved so far).
You don’t even need to hide the crazy questions. Offering them as extra credit is a simple solution that works well.
As far as I'm concerned, curve grading single courses is just as bad as stack ranking at work. And in here, with high concentration of engineers who loathe stack ranking, a disproportionate fraction are somehow in favour of per-course curve grading.
Blind spot? Stockholm syndrome? Go figure.
Whole stack ranking is just weird. Either the people are good enough to do the work or not. If not eventually fire them. On other hand at top the rewarding extra is an problem, but I don't know if you can do that without someone gaming it.
> Whole stack ranking is just weird. Either the people are good enough to do the work or not.
Even at the risk of veering quite far from the thread topic, I am not sure that's the only angle to look at things. In my experience, pretty much anyone who is genuinely curious and has the discipline to work at understanding how/why a ${THING} functions, is going to be good at their job. Some people just don't find what their thing is, and surprisingly many are in jobs where they are not even allowed to figure it out.
As far as I'm concerned, curve grading single
courses is just as bad as stack ranking at work.
In my years of schooling, I never saw curve grading resemble "stack ranking" whatsoever.In stack ranking you have to designate some team members as superior and some as bad. You could have a team of ineffective idiots and be forced to label some of them as high achievers, or a team of superstars and be forced to label some of them as bad. I agree that this is manifestly ridiculous.
I've never seen curve grading like that.
BTW, I don't know if it's a named fallacy, but saying "there's no rational argument for X" is not a good argument against X. You can't prove a negative so you cannot know if there is not a rational argument for X.
But in that same example, if many of the students get close to 100% on the final by cheating, then the remainder of the class will suffer
If an exam turns out to be too hard the teacher can investigate, consult their peers, talk to their students and decide if it's worth to scale all grades by a factor to correct.
It should be, but profs and TAs change from semester to semester. The coursework changes also. Also the profs, TAs, and coursework of prerequisites change too
> It shouldn't be easier for one cohort over another just due to the first being, on average, less prepared than the second.
A good professor will have the sense of discretion necessary to know when a class is half-assing on average
That way you don't incur any of the (pretty severe) drawbacks of a curve but don't punish students for questions that were badly phrased or weren't properly taught.
There is no rational argument for grading people on a class curve
It's an imperfect solution for a legitimate problem.The counterargument is that it would be rare for a prof/teacher to absolutely nail the correct difficulty for an exam.
If they feel that their students' average exam grade fails to accurately reflect how well the class is learning the material, then some kind of adjustment makes sense... imagine a scenario where you have a classroom full of motivated and engaged students who are showing good understanding of the material, and yet the average exam score is 60%. This strongly suggests professor/teacher has erred and an adjustment is in order so that the scores better reflect actual mastery of the material.
There are of course also a lot of situations where grading on a curve is blatantly unfair and/or simply makes no sense.
I would like to see a system where almost all (something like 99 %?) of students just plain "pass". Then we have the lower statistical anomalies (lowest 0.5 %) and upper statistical anomalies (highest 0.5 %) which fail and get an "excellence" type grade.
If the average score is too low or too high, that doesn't mean more students fail or perform excellently, that just means the teacher needs to recalibrate.
(Of course, these percentiles ought to be measured over as inclusive a reference class as practical. Ideally across schools and years simultaneously.)