If it's a legitimate, programming-related question, and it's phrased as an actual question with separate answers, then there would be nothing wrong with it and it would not (should not?) be closed.
Remember that it's perfectly OK to ask and answer your own question, so long as you follow the rules set out in the FAQ, pretending that you're on Jeopardy! and phrasing it in terms of a question.
If you see a question crop up often, then it's generally a good idea to try and generate a "canonical" question with a really good set of answers, that you can then use to close the other questions as a duplicate of. I've recommended this myself several times, and others have as well.
Note, though, that you might be better off finding a good candidate among the questions that have already been asked, editing it a little to clean it up as much as possible, and then posting the definitive answer to that question. There's no reason to post a new one of your own if you can simply retool an existing question.
And once you've done this, you should definitely edit/suggest an edit to the applicable tag wiki (r) and include a link to your "canonical" or frequently-asked question so that people will be able to find it easily.
The only part people may or may not disagree with here is whether you need to make it community wiki if you do choose to post your own new question. Personally, I don't think so. If the question is useful, clear, and helpful to others, then you deserve all of the rep you get from upvotes. It shouldn't be mandatory to mark these as community wiki. You might consider marking the answer as community wiki in accordance with the true spirit of community wiki (so that it has a lower threshold for the reputation privileges required for editing), but I see this as somewhat less necessary now that suggested edits for all users, including anonymous ones, have been rolled out.