3 ms·
My easy (if extremely unpopular) fix: You can only submit your code for a given assignment a maximum of N times, where N is appropriate to the assignment diffi
by mquander 17y ago
My easy (if extremely unpopular) fix:
You can only submit your code for a given assignment a maximum of N times, where N is appropriate to the assignment difficulty and the level of the class. Then you can't pursue a haphazard "try this? nope, didn't work" strategy, and you have to reason out your program correctly on your own without appealing to the black box.
Alternately, if you wish to be less draconian, simply deduct points for every incorrect submission.
- zokier 17y agoThe places I have seen this kind of system in use, they work just like that. Limited number of submissions and flexible pointing system. Those systems gave points according to how many tests you passed, and there was minimum score to pass. The other system I have seen, also scored by coding style, ie. commenting and correct indentation etc. You could see style points and functionality points separately and there was separate minimum points (usually quite high in style). And IMHO these are good tools. But they don't teach you debugging (at least not directly). They teach that you need to test and debug your code before you submit it, which imho is good practice anywhere, ie you should test and debug your code before committing to SVN (or push your changes to main tree in DVCS-talk). Of course that should be told to students, and they should be taught proper debugging/testing-methods. I mean these kind systems do not prohibit doing your own tests and debugging those before submitting, now do they?