Skip to main content
2 of 2
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/

I often mention other answers (if I think they are good) in my own answer. Sometimes I may use a point or piece of code from their answer (always saying so and giving credit).

From my own experience, there are several ways to collaborate in reviews without sharing an answer.

  1. Comment on other answers, praising good points.
  2. Comment on other answers, asking follow up questions which may lead them to expand their answer. They may pass the baton on to you, of course.
  3. Comment on the question, asking for clarification of constraints and input/output examples, particularly where existing answers show a need for them
  4. Be willing to concentrate on as-yet undiscussed aspects of the problem rather than compete over the main points of existing good answers. Explain this in your answer.
  5. If you do post alternative solutions, be generous in reference to existing ones and explain the shortcomings (as well as the benefits) of your own solution in comparison.
  6. Don't be afraid to answer if you can only answer one aspect of the problem, even if it is. The advice is often still very welcome. Somebody who is expert on the main problem may be less adept in your area and find it boosts their answer.

There is absolutely no point getting hung up on not being the accepted answer. If questioners all had good judgement in choosing the best answer, they would probably not need to post here in the first place.

I feel rather lonely in my pet areas, which seem to be relatively niche and have a very small number of reviewers. We'd all benefit from more answers, no matter how narrowly-focused and succinct.

itsbruce
  • 2.2k
  • 10
  • 5