All of us programmers dred the code review time, looking at each line and wondering what those experts out there are going to find wrong with it and how much of their code is going to survive in a recognizable form. Someone somewhere posted this link to an interesting article about how to survive a code review. Some of us learn these things the hard way after 10s of bleeding red reviews, for others, do read this one.
http://www.jsquared.co.uk/jennyl/verity.htm
2 comments:
The little article was a nice read. And your post is very true. But we here use agile methods (http://www.xprogramming.com/) so half of the code review is done at coding time. We sit two people to code a single piece of code.
Yes, I have heard of extreme programming, but still have to try my hand at it. I still feel that two people working on the same code is a waste of time, when one person can do the job. My logic is that, code reviews take like an hour of other person's time, while coding together takes days.
Post a Comment