11

What's the proper way to update a question while testing out suggestions? For example, I asked for Podcast app suggestions. Now I'm trying out a couple of the suggested apps and a few that I found on my own.

Should I start adding an answer for each of the apps that I have finished testing/trying as some sort of review? (for apps suggested as answers I guess I should add a comment stating how it worked out for me instead of adding a new answer) and when I make a final decision should I mark one of the options as accepted?

Or should I just do all my testing and just mark an answer and give some comments?

I'm asking in part because I don't want to leave the question in an apparently 'abandoned' state while checking the options out. Sometimes tryouts take a few days =b

0

2 Answers 2

15

Well, it's pretty normal that testing recommended solutions is not done "ad-hoc". On some SE sites, I've marked questions accepted several months after they've been given: if evaluation takes time, it takes time. So don't feel pushed just because of that.

On the other hand, if you think you might have found an answer being the solution, you can also go ahead and mark it such. If you decide otherwise later (e.g. because another answer popped up matching a lot better), you still can "move your mark".

Leaving a comment on a question you're just evaluating is a nice gesture to the answerer. But there's no need for a "progress bar". When you finished evaluating one solution, and found it not fitting, you can always leave a comment like "thanks, looks great, but doesn't fit because..." to show what was going on. If the answer showed effort in being given, and principially matches your question, you can always honor that by an upvote – even if it turned out to not fully match your needs. Upvoting is the SE way to say "thanks" :)

TL;DR:

I'm pretty sure everyone recommending a software and specifying how it matches your needs is aware you cannot say straight away if it really fits you. So take your time, and don't feel pressed.

2
  • not done "ad-hoc": I am not sure to understand. Do you mean not done immediately?
    – Nicolas Raoul Mod
    Jul 7, 2014 at 2:32
  • @NicolasRaoul No. Rather not COMPLETED immediately. It usually takes time, it's nothing you do as fast as clicking your fingers :)
    – Izzy Mod
    Jul 7, 2014 at 8:50
3

In addition to Izzy's answer, I would say that in some cases you might also edit an answer. Not to change the spirit of the answer, but just to add details like:

  • License information
  • Price
  • For each criteria of the original question, whether the proposed solution fits or not.

It is a way to make answers better, thus making the whole page more valuable to visitors. Comments can achieve the same but make it more laborious for the reader.

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/901/how-to-behave-while-trying-out-recommendations/902
softwarerecs.meta.stackexchange.com
crawl=CC-MAIN-2022-33
111328
application/http; msgtype=response
sha1:KZPTRH57XUEYS2XG7HJTK6DEM375W2N3
<urn:uuid:5b8ce29e-4f8c-4cb7-ab7f-a5ca96d146ca>
2022-08-15T07:12:17Z
151.101.65.69
text/html
sha1:R7NDJAPJFCZW27ZLOLCXTXKEDU6FCJ4J
<urn:uuid:da4c9fec-bf35-4e96-8011-c74f1faa184e>
https://softwarerecs.meta.stackexchange.com/questions/901/how-to-behave-while-trying-out-recommendations/902
response
<urn:uuid:0d48197e-8fee-459a-8a69-6bdd46e2b5ad>
isPartOf: CC-MAIN-2022-33
publisher: Common Crawl
description: Wide crawl of the web for August 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-12
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-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/