Intro programming classes are usually run like that. If your code is so inundated with errors that you can't even get it to compile, you don't deserve points.
The fact that a single test case failing = 5% also leads me to believe it's an intro class since, that's not even expected on a professional level.
I'd have to agree with you on the intro class part since any non-trivial application in the workforce is always going to have some sort of bugs. I remember my QA mentor in my first internship once told me that no big program is completely free of bugs -- it is just the case that the bugs have not been encountered yet, and QA's job is meant to find as many of them as possible before going out to production.
Intro computer science classes are also structured as weed-out classes from what I've seen and that's a different discussion for another day.
Also when it comes to due dates, make sure you completely understand when an assignment is due (for example, does Tuesday mean at class at 12 pm or 11:59 PM on that day?). This will help in preventing late submissions.
One of the most aggravating parts about being a tutor is when students come to me with an assignment due on the same night. There was a case where a student's professor policy was to submit the first version of the program at 12 pm that day and two weeks after to fix any problems. The student didn't submit before that time and sought help from me for 30 minutes on an assignment he'd be getting zero credit for.
Last edited by DossarLX ODI; 12-15-2016, 06:14 AM.
Originally posted by hi19hi19
oh boy, it's STIFF, I'll stretch before I sit down at the computer so not I'm not as STIFF next time I step a file
Step 1) Write all due dates in a planner, or have a roommate you share classes with that can keep you in the loop (ayy)
Step 2) Determine how long each assignment should take to complete (this is more difficult on bigger projects so all the more reason to start early)
Step 3) Get your damn work finished, even if you've underestimated the length of time needed at least submit something.
If you don't finish assignments it's all to do with motivation, you should seriously step back and review your educational and employment goals if you're having issues completing stuff. If you're a grinder and get low marks that's totally different, you should keep pushing for something you want!
Intro programming classes are usually run like that. If your code is so inundated with errors that you can't even get it to compile, you don't deserve points.
The fact that a single test case failing = 5% also leads me to believe it's an intro class since, that's not even expected on a professional level.
it's a 3rd year level class. no intro programming classes are like that lmao
it's this in most of my uni classes, as it should be.
life doesn't care about you. gotta be punctual on your own. I would at least try emailing your professors, assuming your work is indeed done.
I once ended up in a class once at a different university where the late penalty was 2% per day with weekends not counting. Which basically says to me "If I can't finish it Thursday night for the Friday due date, I can trivially just do it this weekend, hand it in on Monday and probably get a HIGHER mark than rushing to get it done on time" it enabled such procrastination it was absurd.
The classes where it was just "Full Letter Grade per day" or "I don't accept late work" did a lot more to actually -get the work done- which is what you need to be able to do to be at all successful in life.
Comment