Timeline for How can I discourage poor design while using automatic grading of submissions?
Current License: CC BY-SA 3.0
19 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 6, 2017 at 19:14 | answer | added | Ray | timeline score: 4 | |
S Jul 6, 2017 at 16:48 | history | suggested | Harry |
i was looking at the tags on the site earlir today and found one for auto graders... thought it fits.
|
|
Jul 6, 2017 at 16:47 | review | Suggested edits | |||
S Jul 6, 2017 at 16:48 | |||||
Jun 26, 2017 at 21:34 | answer | added | tusharsoni | timeline score: 3 | |
May 30, 2017 at 9:17 | vote | accept | Aurora0001 | ||
May 30, 2017 at 9:12 | answer | added | ctrl-alt-delor | timeline score: 5 | |
May 29, 2017 at 7:03 | answer | added | Miles | timeline score: 6 | |
May 28, 2017 at 18:28 | answer | added | Ryan Nutt | timeline score: 2 | |
May 28, 2017 at 13:16 | answer | added | Ben I.♦ | timeline score: 9 | |
May 28, 2017 at 11:55 | comment | added | user223 | @Aurora0001 Programming is about efficiency, and the shorter answer is generally more efficient than a long, work-around one. | |
May 28, 2017 at 10:51 | comment | added | Aurora0001 | @subscript You should post that as an answer, since it seems like a good idea. Ideas on how to find an appropriate size limit would be interesting, too—my solution may be much shorter than theirs, but a longer solution might not be unreasonable necessarily. | |
May 28, 2017 at 10:47 | comment | added | Aurora0001 | @thesecretmaster More general solutions would be ideal, but Python would be the language I'm most interested in evaluating. | |
May 28, 2017 at 10:47 | answer | added | thesecretmaster♦ | timeline score: 3 | |
May 28, 2017 at 10:34 | comment | added | thesecretmaster♦ | rubocop is a static code analyzer. It works by looking at the code without running it and evaluating for best practices, etc. | |
May 28, 2017 at 10:28 | comment | added | ItamarG3 |
@thesecretmaster perhaps looking into how rubocop works could be insightful
|
|
May 28, 2017 at 10:27 | comment | added | thesecretmaster♦ | What language? For ruby there is a static code analyzer that checks for best practice called rubocop. Maybe there is a similar utility for the language of your choice | |
May 28, 2017 at 10:23 | comment | added | ItamarG3 | I would suggest solving this with programming. I would make a neural network that would evaluate the students' answers. But I feel like that's overkill. Then again, that is sometimes my style ;) | |
May 28, 2017 at 10:00 | comment | added | user223 | Setting a limit on the size of the program should force them to not make large and unnecessary programs or functions. For the example you gave, set the limit to 50 characters, or something around that range. That will make them try to shorten the program as much as possible. | |
May 28, 2017 at 9:21 | history | asked | Aurora0001 | CC BY-SA 3.0 |