Timeline for How to find positive things in a code review?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 25, 2016 at 13:55 | comment | added | Disillusioned | @DewiMorgan I disagree with "newbies should not pick up reviews for a while". Newbies doing reviews is an excellent way for them to gain familiarity with a code base. That said, they shouldn't be the only reviewer! And that said, I'm in any case also wary of having only one reviewer most of the time. | |
| Oct 21, 2016 at 15:41 | comment | added | Dewi Morgan | Unsure why this was downvoted (downvotes with no comments are ludicrously silly on a thread about good code review). Everyone reviewing should be standard procedure. On a Kanban board, there would be a column for code review, and whoever in the team picks up the next item should do the review (with caveats; newbies should not pick up reviews for a while, and then should start on those which require little domain knowledge). On a scrum board, essentially similar: work right to left. | |
| Oct 18, 2016 at 10:54 | history | answered | Stig Hemmer | CC BY-SA 3.0 |