Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

77%
+5 −0
Q&A Split any question post with two or more questions into several posts (per the number of questions) and attribute it to the asker

Sometimes several questions are closely related and are best handled as a group, as this answer says. Sometimes the asker (who is, pretty much by definition, less expert than the people who will a...

posted 2y ago by Monica Cellio‭

Answer
#1: Initial revision by user avatar Monica Cellio‭ · 2021-10-03T02:45:14Z (over 2 years ago)
Sometimes several questions are closely related and are best handled as a group, as [this answer](https://meta.codidact.com/posts/284425/284435#answer-284435) says.

Sometimes the asker (who is, pretty much by definition, less expert than the people who will answer the question) can't *tell* whether questions are closely related and should be handled together.  I've been in that position at times.  I've found it's best to approach this case by asking a main question, identifying what I think are sub-questions, and asking for correction if they're not really related so I can edit them out and ask them separately.  An asker in this situation is probably monitoring notifications and can respond pretty promptly if it turns out edits are needed.

Sometimes the asker hasn't thought through it, or asks a bunch of things together that aren't really related.  I think the asker is the one who needs to sort that out.  Community members should try to provide constructive feedback in comments, but we shouldn't try to make large fixes on behalf of the asker when we don't really know the asker's intent or which parts of the question are most important.  The most I would feel comfortable doing in a third-party edit is to remove all but one question (the text is still available in the edit history) and invite the asker to ask those questions separately -- but I wouldn't create those questions myself unless I had another reason to do so (see final paragraph).

If a question isn't in a state that it should be answered, it should be closed pending corrective edits.  This avoids the problem of sorting out answers to these multi-questions later.

If the asker doesn't address the issue after some time and somebody wants to answer one of those questions, that person can re-ask that part and then self-answer.