Timeline for How can we motivate students to review each other's code?
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Aug 30, 2017 at 16:32 | answer | added | Agent_L | timeline score: 1 | |
Aug 30, 2017 at 14:56 | answer | added | Samantha Eastwood | timeline score: 4 | |
Aug 30, 2017 at 1:33 | answer | added | srattigan | timeline score: 1 | |
Aug 29, 2017 at 21:52 | comment | added | Dunk | Your findings are not unique to students. The workforce is exactly the same way. Some developers believe strongly in code reviews and do a good job while others look at them as yet another task they don't have time for and barely do a review if they do one at all. If you find that silver-bullet that gets everyone excited and motivated to do code reviews then you will be able to leave your teaching job and make a lot of money consulting. IME, neither the carrot nor the stick has much impact in changing behavior regarding code reviews one way or the other over the long-run. | |
Aug 29, 2017 at 21:14 | answer | added | ZeroOne | timeline score: 1 | |
Aug 29, 2017 at 17:38 | comment | added | Kevin | It would be a huge help if students could look over each other's code on projects to help each other out before handing them in. Unfortunately, the (very appropriate) culture in schools that treats cheating and plagiarism very strictly makes this difficult to do. | |
Aug 29, 2017 at 17:05 | answer | added | Stilez | timeline score: 3 | |
Aug 29, 2017 at 15:05 | vote | accept | Safirah | ||
Aug 29, 2017 at 15:02 | answer | added | RageCage | timeline score: 9 | |
Aug 29, 2017 at 14:57 | answer | added | Michael0x2a | timeline score: 9 | |
Aug 29, 2017 at 14:48 | answer | added | Peter Taylor | timeline score: 7 | |
Aug 29, 2017 at 14:32 | answer | added | Buffy | timeline score: 16 | |
Aug 29, 2017 at 14:02 | history | asked | Safirah | CC BY-SA 3.0 |