Timeline for How to find positive things in a code review?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 18, 2016 at 17:27 | comment | added | robert bristow-johnson | Your team(manager) should communicate that producing bugs is part of the game, but finding and fixing them will save everybody's job. This is true and it means that everybody is a stakeholder. But it should not be the responsibility of someone pointing out a bug (or, just bad spaghetti code) to write a test case to prove to the original coder that it's a bug. (only if it is widely disputed that it truly is a bug.) | |
| Oct 18, 2016 at 8:01 | comment | added | Eiko | He is asking the wrong xy-problem, see meta.stackexchange.com/questions/66377/what-is-the-xy-problem | |
| Oct 17, 2016 at 22:21 | comment | added | Aaron Hall | "The whole point of code review is to find problems" true - but none of this answers the question as asked. | |
| Oct 17, 2016 at 18:56 | history | answered | Eiko | CC BY-SA 3.0 |