I’ve just read an very interesting article talking about Code Reviewing. I usually do it, review my source code and my teammates’s. It’s not boring as you imaging, contrariwise, quite exciting.
There’s a lots of code is created everyday, so I pick some parts to do the job based on my experience, the one I think it’s important and need to be review again.
When I am doing reviewing, not only to find mistakes or logic implementation’s issues, but also I am figuring which one is GOOD and which one is needed to be apply to the similar parts.
When I do that, It means WE are learning together, doesn’t mean I am trying to figure out your mistakes 🙂