I think the most important question when reading an answer is Will this answer make the code better? If the answer is yes!, that merits an upvote. But if the answer is meh??, I think the answer needs to be reconsidered.

Oftentimes, with questions that do have serious issues worth mentioning, answers get posted that are trivial. By trivial, what I mean is that an answer mentions an issue that is accurate (e.g. "your variable s should be named size", or "your 15 line C++ program shouldn't use using namespace std;") but extremely minor compared to other potential issues (e.g. having a really bad algorithm, repeating code unnecessarily, poor code structure, failure to encapsulate data, undefined behavior, not realizing the standard library has a function doing what they want to do, etc).

I'm not going to link any here, but I see a several such such trivial-only answers every day. I think we as a community should actively discourage such answers, by downvoting them. Because, ultimately, the point of CodeReview is to make code better - and if you're not making the code better, if you're not addressing the actual problems in the code by just grabbing the low-hanging free-rep fruit, then you're really not helping anybody.

Thoughts?