14

I have just seen this answer Password manager for Linux with just working in-browser autotype Using the tool myself I'm sure I could write a better answer (more detailed, with screenshot...).

So should I edit the one already there or should I add a new answer that says the same and more details?

1

3 Answers 3

10

It depends how far the answer is from being a good answer.

If the answer explains how 4 out of 5 requirements are met but doesn't discuss the fifth, edit it. If all you'd want to add to the answer is a screenshot, add one. These are minor defects, and we are encouraged to edit to “clarify the meaning of the post”, “include additional information only found in comments”, “correct minor mistakes”, “add related resources”, etc.

If the answer just says “use this product” without explaining why, this is not at all the kind of answers we want on the site. Flag it as “very low quality” and write a proper answer.

In between there's a range where it can be ok to post your answer even if the first answer is to stay on the site. An answer is defined not just by the product it recommends, but also in the way it recommends it.

In the case of “gnome-keyring is a good password manager that comes with Ubuntu”, I encourage you to post an answer about Gnome Keyring that matches the level of detail of the LastPass and KeePassX answers.

2
  • 1
    +1 | Nicely described -- I agree all the way.
    – e-sushi
    Feb 10, 2014 at 14:34
  • 1
    +1. Another example is my Perl for Windows question. First answer was VLQ. Second recommended same thing but was much much higher quality.
    – DVK
    Feb 10, 2014 at 15:26
5

As for editing other people's posts - I believe edits should not deface, misinterpret or paraphrase entirely what has been mentioned by another person. An edit makes sense when the answer has broken links, horrible grammar, formatting problems and other reasons that may prevent the readers to better understand and apply it. Usually the review system of the Stack Exchange sites allows for reviewers to flag invalid, too minor or destructive edits appropriately.

That being said, your edit might have all the good intentions, but it could never make it live due to the review system itself. Apart from that, the author of the post might disagree with your suggestion and your edit could become a reason for frustration, and series of comments like "hey, I never had the intention of posting this, revert it please".

A new answer will avoid the above issues. I'd personally write my own answer, in case it will significantly differ from the existing one in the following cases:

  • I am adding extra related information that the other answer omits
  • I am adding specific information for potential problems that may be encountered during the application of the solution, and list at least one work-around
  • Address the issue with respect to the OP specific scenario (usually I write comments to the question first to get details if not present). Of course, the existing answer has to miss the points I am willing to add, or have them too obscured.
  • I had the same issue and I feel confident at properly addressing it.

In other words, if the answer can be of value to he OP or users with similar problems, then it is good for the community to share your experience and expertise. If the answer is not that good, the community will react accordingly anyway, so obviously this is a good-enough criteria if you doubt whether "to answer or not to answer" - if it will be good for the community then do answer :)

In cases where the answer is close to yours, and the differences or improvements are insignificant enough not to write a separate answer, you could address your concerns as comments. If the author does not reflect them, they will still be available as a comment, and as such will add to the answer.

4

You should give the original answerer a chance at writing a better answer (seems like that has already been done). If they don't, and you think you can make a better one, by all means do so.

I don't think you should edit their post, since:

  • A: They didn't do any work towards a good answer.

  • B: It won't have a proper score, since the votes it has already are for the old, bad answer.

2
  • 1
    "give the original answerer a chance" - this should ideally be quantified. 5 mins? An hour? A day?
    – DVK
    Feb 10, 2014 at 15:27
  • @DVK I usually give them a day or so. It's a bit relative however.
    – Seth
    Feb 10, 2014 at 16:32

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .
https://softwarerecs.meta.stackexchange.com/questions/328/should-we-add-a-second-answer-with-the-same-recommendation-if-the-first-answer-i/330
softwarerecs.meta.stackexchange.com
crawl=CC-MAIN-2022-27
129722
application/http; msgtype=response
sha1:KCF5SEVRH7T6KWUNH7K5WA4BQHO3HSUB
<urn:uuid:b1c10feb-e125-479a-8777-3e5b90bdad1c>
2022-06-25T07:20:25Z
151.101.1.69
text/html
sha1:UXCSFVW5QAM4P7P3K2COKGXFOGGYHOIC
<urn:uuid:967a2e73-f439-45f8-8b4d-2c74dfceb83b>
https://softwarerecs.meta.stackexchange.com/questions/328/should-we-add-a-second-answer-with-the-same-recommendation-if-the-first-answer-i/330
response
<urn:uuid:510bdc81-590b-454c-8617-16fe853ddfda>
isPartOf: CC-MAIN-2022-27
publisher: Common Crawl
description: Wide crawl of the web for June/July 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-140
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/