Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
(Elsewhere...) You look over a post on Code Reviews, and you don't find any problems. Should you post an ‘it's fine’ answer, stay silent, or do something else? Seems to me there's some value in hav...
#1: Initial revision
by
r~~
·
2020-10-21T18:06:35Z (about 4 years ago)
Code Reviews: ‘it's fine’
[(Elsewhere...)](https://codereview.meta.stackexchange.com/questions/94/should-your-code-seems-fine-answers-be-acceptable) You look over a post on Code Reviews, and you don't find any problems. Should you post an ‘it's fine’ answer, stay silent, or do something else? Seems to me there's some value in having a signal that *n* people have reviewed this code and found no issues; better for the asker to see that than to have their question go zombie with no feedback, right? But maybe it matters *which* people have reviewed this code—maybe you trust the reviews of high-rep users more, or there are particular users that you know and trust/distrust? On the other hand, maybe an ‘it's fine’ answer with no explanations of what's good isn't actually all that valuable to people, regardless of who posted it? Maybe we want to de-emphasize the identity of the reviewer and focus on the code and the potential issues with it? I think we should try to come to some sort of consensus on this (which may or may not be the <nowiki>Code Review.SE</nowiki> consensus) and add that to our Help documents.