Take a look at “Facts and Fallacies of Software Development” Robert L Glass, where it is clearly shown based on multiple researches and examples how p2p code reviews are one of the most efficient ways to eliminate bugs and bad design earlier.
-
-
I agree. Code reviews are no panacea. I've only seen them be useful when they are done in person, where you have to explain your code to someone else, but it's mostly just 'rubber ducking'. They are rarely useful when there is no interaction.
-
And this is something you can learn to do yourself. When I check in code I review each of my changes and write a detailed changlist as though I am describing to someone who doesn't know anything.
- Show replies
New conversation -
-
-
The fact that you need code reviews is already the obvious sign that your project is doomed. And nothing will save it from that. To make good software you need: no open-source, small team, all real deep experts. There is no other way.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.