This question already has an answer here:
- Exit strategies for “chameleon questions” 12 answers
The title of the question is hard to comprehend, please read on.
I'm rather new to Stack Overflow, I joined just about a month ago, and since then I have been fairly active (top 0.41% of the current week's ranking).
Since joining Stack Overflow I've come across a lot to see, I've starting noticing some trends in the questions being asked, the obvious ones are the broad questions, duplicate questions, and others, albeit a peculiar one which I've come across would be the recurring questions, this is how it works:
- A given user will ask a question about a problem they are having while coding (this is a good thing, Stack Overflow is exactly the place for such problems)
- There is an answer given by another user which solves the problem.
- The user who asked the question marks the given answer as accepted and continues coding (amazing till here! but hold on to your seats because this is when it gets messy)
- With the code/solution provided by the answerer, the user who asked the question implements it and it works.
- It works well but soon after writing some lines of code something else goes wrong.
- The user hops back on to Stack Overflow and starts to comment on the post of the answer which was accepted earlier, posts about the new issue which has come up.
- The answerer gets back to the problem, reanalyzes it and solves it once again.
- Read from step 4.
In the process of revisiting step 4, the user is highly likely going to edit the question content with additional updates.
The entire question changes, initially the question was:
a single well defined issue encountered while programming <- the question and its answer can be highly useful to other users in the future.
however with all the subsequent tries and updates it turns into:
a large blob of issues one after the other all in a single question <- equivalent to multiple separate good questions asked, as a sum of parts its not what other users facing one of the problems can relate to, as everything explained in the answer is tangled up like earphone wires.
About the the user who answers to all the updates. Personally, its something through which I've been through, I do not want to point my finger (I meant hyperlink) as I do not think that would be right here, however If you dive into the questions I've answer on my SO profile you won't have a hard time finding it (think sorting by activity?)
I would loose respect for myself If I ignore the updates made by the user and not answer them all. However at the end of the day I would rather have the user opening up a separate question, because its almost a whole different question now.
The main similarity between broad questions, duplicate questions, questions of these types and the mentioned
recurring question is the quality deteriorating affect they have on the base of Stack Overflow.
The main difference is that broad/duplicate questions have flags to deal with them, whereas recurring questions seep through underneath unnoticed almost every single time. Valuable Q&A is lost in entanglement with the updated answer, all that was needed was, the user asking the question to post a separate question with the new issue.
Which is better for Stack Overflow?
"MySQL syntax error, help?" -> answer given -> question updated (wants to know why the column names are different now) -> answer updated -> question updated (on testing with an initially empty table the given query's aggregating fails) -> answer updated
- "MySQL syntax error, help" -> answer given
- "Column names different from expected query in MySQL query" -> answer given
- "This mysql query with empty tables results in aggregation that works in an unexpected way" -> answer given
Something for you to ponder upon: what should be the title of the former question?
Note: there is another question which revolves around the exact same concept. This other question discusses about "exit strategies", which this question is not about.