Gregory's ServerWho called it “code review” instead of “objection-oriented programming”
 17 comments
@inthehands Is this the same team that has Agile standups not devolve into droning rounds of status reports?  @inthehands the ease or difficulty of code review depends greatly on the outlook of the team: both the reviewers and the reviewed. I’ve seen review greatly improve code and everybody learns things, I’ve seen bad reviewers turn people off the process entirely, and I’ve seen reviews become endless fights when the code author comes in thinking “this is a massive waste of time, my code doesn’t need it.”  @MyLittleMetroid   @inthehands @jongary Sigh. Still waiting for the +3 so I can finally land this damn feature before the code freeze, can I PLEASE get someone to review this? @inthehands Same person who came up with "linter" when "complainer" feels like a more accurate accessory to the compiler!  |
(The serious answer to this frivolous question is of course “somebody on a good team where code review was supposed to be constructive dialogue and not just endless nitpicking“)