News for hackers. Stuff that matters.
Re:Ask HN: How do you build a healthy code review culture? by seanwilson on Thursday March 10, 2016 @11:11PM (#11264601)
"If there's no document to point at, no objective standard to meet or not meet, I'm not reviewing it because it's just not worth the tantrums and screaming from precious programmers."

What about rules for less objective things like how readable a function name is though? If someone wants to be difficult addressing code reviews, there's always plenty of subjective feedback they can do this for.

Re:Ask HN: How do you build a healthy code review culture? by dmm on Friday March 11, 2016 @07:13PM (#11270560)
The Google c++ styleguide[0] has some examples, in general and specifically for files, functions, etc. Looking over them most are pretty objective so maybe it's worthwhile to come up with some usable rules that enforce qualities you notice readable code shares, even if they aren't completely comprehensive.

[0] https://google.github.io/styleguide/cppguide.html#Naming