Code review meetings?

Anyone interested in setting up meetings specifically for code review (rather than working through new problems or presenting techniques, which is more typical R Club)?

I’m thinking about this because I’ve been writing A LOT of code for my dissertation, and it’s all publicly available on my github repo — this is not the same as it actually being useful/interpretable to other researchers, though, which is my hope. I think I do a pretty good job of being consistent within my own code, but I’m thinking that’s really not enough to actually make sure other people will be able to understand it. Code reviews might help me, and others in the same boat, end up with code that is clearer and cleaner, and has gotten over the initial test of another person reading it and being like, “wait, what?”

So what I’m thinking about is a group of people who are all actively writing code for real projects (or have existing code from a completed project that they would like to clean up), and we meet to go through each others code and provide feedback about what’s clear and what’s not, and where to improve the code if it can be done better. We might want to have an initial meeting where we agree upon some style guides (a couple ideas of places to start: variable names in general, r code in particular, and as always, there’s an r package for that).

Interested? Leave a comment, or email me directly: rosem@uoregon.edu In a week or so, I’ll send around an email to interested folks so we can coordinate.

2 comments

Post a comment

You may use the following HTML:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>