Timeline for How do you make people accept code review?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2014 at 19:59 | comment | added | Dennis | "If the only input code reviews provide is something which can easily be accomplished by using a tool, then code reviews are a waste of time." Yet if you don't use a tool, then minor violations of the guidelines should still be called out. Of course it's better to use a tool if you can, no one wants to be that guy/gal that's always calling out the little inconsistencies. | |
| May 2, 2011 at 0:37 | history | made wiki | Post Made Community Wiki | ||
| May 1, 2011 at 15:08 | history | migrated | from stackoverflow.com (revisions) | ||
| Aug 21, 2009 at 11:04 | comment | added | Emile Vrijdags | +1 the most important argument: a good way to learn from each other! | |
| Aug 21, 2009 at 8:27 | comment | added | user7197 | "The code improves and we probably both get a little smarter". I totally agree. I have learned a lot of things from code reviews. If my code was reviewed I could see what I did wrong, learn from that and tried hard to avoid it in the future. But I also have learned a lot from performing code reviews, because I saw better ways of doing (my) things. My experience increased by “stealing” skills from the others (I can’t imagine how many books I should have read or how time should I've been practicing to gain the same skills that I have learned from others better than me). | |
| Aug 21, 2009 at 7:57 | history | answered | Brian Rasmussen | CC BY-SA 2.5 |