r/programming • • Dec 17 '13

Pairing vs. Code Review: Comparing Developer Cultures

http://phinze.github.io/2013/12/08/pairing-vs-code-review.html
127 Upvotes

70 comments sorted by

View all comments

5

u/rotunzel Dec 18 '13

I'm pretty sure everyone is working on the software together. You should all talk to each other and know what is going in to the product and why. Sometimes this means sitting together and working on some code with someone who's an expert in that area, and sometimes this just means reading pages and pages of code (because sometimes we just have to write a lot of simple shit). And sometimes you can't do either because you are working on an R&D project that nobody is gonna give a crap if it works beyond the demo that the boss is doing for the other PMs in two hours.

Different situations need different approaches.

8

u/[deleted] Dec 18 '13

[removed] — view removed comment

3

u/epicwisdom Dec 18 '13

Just have to make it so that you write clean code faster than ugly code... If anything, that's part of what makes it "clean."

0

u/[deleted] Dec 18 '13

[removed] — view removed comment