by baberuth on 4/11/11, 2:06 PM with 14 comments
by frobozz on 4/11/11, 2:42 PM
by rch on 4/11/11, 2:16 PM
The trick is, could there be some sort of bilateral confidentially agreement? That's one I'd need to ponder a bit.
by davesmylie on 4/11/11, 10:32 PM
You can review and give decent feedback on a small snippet of code fairly easily and quickly, but that's of limited value in a real project.
To be able to give a decent review (eg beyond a cursory "You should name that variable better, or your indentation sucks), requires that either the amount of code you are reviewing is so small that you can grok it quickly (limiting the value of the review), or that you spend at least some time familiarizing yourself with the rest of the code base so be able to gauge the impact of the code changes.
This is all good if the person you're trading reviews is prepared to spend the same amount of time on your code, but for example, I find it very frustrating when I spend 30-45 minutes giving a detailed review of a website on http://feedbackroulette.com (a similar concept, but for websites reviews), only to get back a 3 sentence review in exchange that was clearly bashed off in about 30 seconds. Awarding points for reviews goes someway to alleviate this, but still it's a real pita...
by BasDirks on 4/11/11, 5:21 PM
by Stuk on 4/11/11, 4:08 PM
(aside: I can't actually work out if people who complete reviews at 5 sec tests get paid? Or if they do just get karma)
by omouse on 4/11/11, 5:21 PM
If anyone has some bitcoins and wants a code review, send me an email: omouse@gmail.com
by dy on 4/11/11, 3:08 PM
by bguthrie on 4/11/11, 5:58 PM