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 »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Is my question a duplicate? What now?

Post

Is my question a duplicate? What now?

+5
−0

As part of a general effort to produce basic Q&As for Python, recently I've been focused on issues related to starting up an interpreter and running the code - so, questions about setting up an environment with third-party libraries, figuring out an entry point for the code, and so forth.

In particular, I've just now written Understanding the if __name__ == '__main__': idiom, in my own style. But I completely forgot that we already have What is the purpose of if __name__ == '__main__'? (which in fact is one of the highest-rated questions in the tag currently).

There are some minor differences:

  • My question is a deliberately written self-answered attempt at a canonical; the other arose organically

  • My question is written with a consistent (I hope) editorial style to match the other Q&As I've been writing

  • The prior question was focused on understanding existing (seemingly useless) code, whereas mine supposes that the reader is also interested in using the same idiom in new code

Normally, these factors wouldn't hold me back: I'd consider my own question clearly a duplicate, and I wouldn't presume that my own work was such high quality as to justify closing the other question. But I wanted to get the community's opinion.

Should I close my own question as a duplicate of the other? Should I migrate my answer and adapt it for the details of the original question? (I'm not sure how I'd naturally fit all of the content in.) What else seems appropriate here?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Articles/Wikis (2 comments)
Articles/Wikis
trichoplax‭ wrote 6 months ago

Another option is to keep organic, naturally messier questions in the Q&A category, and have a separate category for more formal, documentation style articles.

Some Codidact communities already have a category for articles (which differ from questions in that they do not support answers, only comments). For example:

  • Meta has a Blog category
  • Code Golf has a Sandbox category
  • Proposals has a Descriptions category
  • Languages & Linguistics has a Resources category
  • Electrical Engineering has a Papers category
  • Cooking has a Recipes category

If this community decides it would like a similar category it's just a matter of switching it on (doesn't require a code change).

Considering that the primary usefulness of Q/A is that it's easily searchable, and that giving people a quick answer for a quick web search is where it shines (and arguably, is the main goal), I don't see how splitting it between categories is useful at all. It doesn't solve the issue of duplication, which is one of the main problems answer-seekers have. It may look good in the eyes of curators that like to label stuff and put it in the right boxes, but it doesn't help anybody else.