When I was looking for some advise on code reviews, I encountered this article:
Effective Code Reviews Without the Pain
It was a fresh idea to me that reviewing process could be positive rather than negative. I think finding bugs is the primary reason to review codes, which makes me feel it's like a trial in a court. There should be bright sides indeed, as described in the article.
Nevertheless, finding bugs and getting rid of defects are important, and I needed to know how to improve the process. Another article on:
http://opensource.mit.edu/
seems like a good start...
0 件のコメント:
コメントを投稿