Recent searches
Search options
Who called it “code review” instead of “objection-oriented programming”
(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“)
@inthehands perhaps you should include a period before that last quote.
@interfluidity And fix the indentation, amiright?
@inthehands i didn’t want to be pedantic.
@Alonely0 @inthehands i suggest a compromise:
--> '.'
@interfluidity easiest opportunity to be a "contributor". 
@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.”
@inthehands So tired of nit picking code reviews.. makes me want to find a new job.
@inthehands joke’s on you I’ve been programming in Objection-C for years.
@MyLittleMetroid
Ah, yes, the language known for the dynamic modification of dispatch tables known as “method kibitzing”
@inthehands Same person who came up with "linter" when "complainer" feels like a more accurate accessory to the compiler!
@airadam
Ha, going to use this one, for real
@inthehands oh I'm totally calling it objection-oriented programming from now on
