this post was submitted on 27 Jul 2023
101 points (98.1% liked)
Asklemmy
44151 readers
1752 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"Ok class, for the rest of the semester, we're going to use the C89 standard".
I forgot the
return 0;at the end of my main function and lost points on a test. Decided to be a point slut to ensure an A in the class and argued that it's allowed in the C99 standard. The professor sighed and gave me back my points, but next class specified the exact standard he was grading by.I have to admit it sounds stupid to deduct points for that anyway, a test should measure your ability to reason, not your ability to remember trivial formalities.
Yes, but it's easier/less effort to grade that way which is why so many do it
Unfortunately C needs you to remember a lot of formalities and best practices to keep things from blowing up in your face. So I think it makes sense in this case.
I definitely agree that breaking best practices in a way that could lead to UB or hard-to-find bugs should give point deduction. The sole requirement shouldn't be "write standard compliant code".
However, a test does not simulate a real-world development environment, where you will have time to look through your code with fresh eyes the next day, and maybe even have someone review your code. The only thing a test reasonably simulates is your ability to solve the "thinking" part of the problem on your own. Thus, deducting points for trivial stuff that would 10/10 times be caught, either by the compiler, the developer or the reviewer, but isn't "strictly correct" just seems pedantic to me.
To be fair, other than the example by OP I have a hard time coming up with things that wouldn't be either caught by the compiler or are very bad practice (which should give point deduction).
89 or 99? Gotta ask if we're being pedantic ๐