Hi,
I have a 20% position at the informatics department here in Oslo (the rest is
at biology), where I (co)supervise Master and PhD students from the Biomedical
Informatics group. The group has about a dozen MSc students, involved in a
range of different projects, but most will have a coding component. We recently
discussed whether we could have the student review each other’s code ('Code
peer review'? 'Peer code review'?) as a way to improve their coding skill, in a
hopefully low-threshold way (rather than have the professors look at it).
About the format, we feel students should show each other small bits of code
(not all of it at once), e.g. one not-too long function that makes for a doable
review exercise: understand the context and what the code is supposed to do,
perhaps even test it, should not take too long time for the reviewer. The
students can do the entire review process as a pair, or the reviewer looks at
it before they meet to prepare questions and suggestions for improvement. Once
in a while we could ask students to demonstrate an example of what they found
to the whole group, e.g. a piece of code before-and-after.
We were wondering whether others have tried such an approach, or whether it
sounds hopelessly ambitious...
Thanks in advance,
Lex Nederbragt
--
Lex Nederbragt
Centre for Ecological and Evolutionary Synthesis (CEES)
Dept. of Biosciences, University of Oslo
P.O. Box 1066 Blindern 0316 Oslo, Norway
Ph. +47 22844132 +47 48028722 Fax. +47 22854001
Email [email protected]
http://flxlex.flavors.me/
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
