Timeline for How can I tactfully suggest improvements to others' badly designed code during review?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2015 at 10:56 | comment | added | Mawg | #5 - the prime purpose of code reviews is to ensure that the design document has been implemented (correctly) | |
| Apr 17, 2013 at 0:15 | comment | added | Ruan Mendes | #4 cross training developers on new features | |
| Oct 11, 2011 at 14:13 | comment | added | DVK | @Caleb - good point. I didn't want to make TOO many points, so this one got edited out of the outline, but it's still a valid point. | |
| Oct 11, 2011 at 13:13 | comment | added | Caleb | On #3, code reviews aren't just for teaching the code's author. A review can be a good way for less experienced developers to learn, and for experienced programmers who are new to the team to come up to speed on coding standards. Discussing problems as a group can also lead to insights about the product. | |
| Oct 11, 2011 at 5:50 | history | answered | DVK | CC BY-SA 3.0 |