Programmers and Stack Overflow may overlap significantly, but they are also crucially different:
Stack Overflow moderators are psychotic lunatics,
Programmers moderators are paranoid psychos.
On a (perhaps) more serious note, here's a brief list of awesome (and recent) Programmers questions that don't fit Stack Overflow:
Critique of the IO monad being ...
You asked this: https://meta.stackexchange.com/questions/195153/should-so-recommend-alternatives-for-questions-it-doesnt-cover
SO does not accept "tool recommendation" questions. [snip] I shamefully admit there are occasions I go ahead and ask them, even knowing they will be closed, simply because sometimes I still get the answers I need".
It is the renamed and re-scoped Programmers, yes.
This happened after a lot of discussion about this within the site meta.
Given it has a new scope, if one is to ask a question there, I suggest reading their help center to see what's on topic before posting.
See here for a full list of past renames across Stack Exchange.
For an alternative answer: we try to build sites that we feel will succeed based on their audience. In this case, Stack Overflow proved to be a very practical sort of Q&A site -- my thing doesn't work, how can I fix it, what should I use to make my thing do X, etc. (Yes, this is an oversimplification -- it is wholly for effect.)
Programmers, on the ...
You seem to approach asking questions in a volley of fire sort of way, where I think you may be better off taking a sharpshooter's approach.
With the volley of fire approach you fire off a lot of questions and if you're lucky or if you just put enough questions out there you're bound to hit something.
With the sharpshooter's approach its more of a "one ...
This is exactly why we spent eight months refining the documented scope before changing the name: folks generally thought Programmers was a different site from the one it had become.
The change to the name, description, tour, etc. all combine to emphasize that this is NOT the site you thought you knew.
We want folks to approach Software Engineering with ...
Short answer: No.
Once someone posts an answer to your question, your ownership in what will hopefully become a lasting artifact on the site is now half. Once two answers are posted your ownership in that page is about a third, and so on, and so on.
Don't deprecate great information in an effort to improve bad. If the answers really wouldn't apply to the ...
Either that or we need to find another solution so that people actually answer programming questions on Programmers.
Sanity check: out of over 21 thousand questions on Programmers, there are only 204 unanswered questions there.
That's kinda impressive...
No I wouldn't like to send people to Programmers from Stack Overflow's FAQ until Programmers gets their site sorted out a bit more
As of the beginning of this year, the rate of questions Closed, Deleted, or Downvoted below 0 on Programmers is over 50%
Since having your question closed, deleted, or downvoted below 0 is never a pleasant experience, that ...
The very first bullet point on the Programmers FAQ is:
algorithm and data structure concepts
So it fits there. Stack Overflow is more geared towards algorithm implementation rather than the theoretical/whiteboard aspect of it. Since the question didn't specify an implementation language, or any information about the technical data ...
The one has no bearing on the other. You can ask questions at Stack Overflow that are on-topic for Stack Overflow.
It's beyond me why anyone would think that being banned from one site creates "special circumstances" that justify posting questions that are topical for that site at some other site where they're off-topic, using the argument "But I don't ...
Stack Overflow is for programming problems. Problems that an individual has during the process of designing code or doing software development where the solution is very likely to be expressed as a code change.
Programmers is for problems programmers have that don't have a software or code fix, and aren't common to other professions.
You may believe that ...
Closing isn't a dead end. Closed questions can be reopened. Therefore there shouldn't be a blanket ban on closed questions appearing on the home page.
If you think there's a salvageable post in there edit it and vote to reopen (if you have the necessary reputation). If you don't have the reputation, suggest an edit and flag the post for moderator to review....
It looks like this was mostly caused by Anna Lear ♦ cleaning up the tags (e.g. removing sparetime and self-teaching) on some old questions, which automatically get bumped to the front page. I agree that it gives a bad first impression, but bumping edited questions to the front page is definitely by design.
Is a high close/migration rate a problem for a SE site?
Dealing with questions outside the scope of the site is a waste of everyone's time. Instead of spending time making the Internet a better place and contributing in your site's area of expertise, you're wasting time reading, evaluating, arguing over, attempting to fix, closing, and deleting ...
Yeah, it looks like a Stack Overflow question to me. He's asking a specific question about the C# language, and it even includes code.
I'll admit to not really understanding the Programmers guidelines all that well, but if it fits on SO, it should stay there.
This definitely belongs CodeReview with the tag: comparative-review this fits exactly what the site is about.
Just for sanity, going through the checklist:
Is code included directly in my question? (See Make sure you include your code in your question below.) - check
Is the code your code (you wrote it, or you 'own' it) - hmmm?
Is it actual code from a ...
As shown here, Programmers is by far not the most used nor the most successful migration path from Stack Overflow.
We replaced it with TeX, which sees a lot more successful migrations and is going to be a more valuable migration path in the future.
If you see a question that you're sure belongs on Programmers (check the FAQ!), you can flag it for ...
Fortunately we do have migration stats to work off of:
(migrations from SO over the past 90 days)
superuser.com × 222 - 8% rejected
dba.stackexchange.com × 158 - 9% rejected
tex.stackexchange.com × 115 - 7% rejected
meta.stackoverflow.com × 89 - 29% rejected
codereview.stackexchange.com × 70 - 2% rejected
programmers.stackexchange.com × 41 - 7% ...
We have had several such questions in the past, and while "A vs. B" questions are not what we like the most, they are often acceptable providing that the code is real, actual code and not "example code" that has been stripped of context.
In addition to your language tag, use the tag comparative-review and read through some of those questions to see which ...
Hard to say without actually seeing the question, but since you're using words like "design" and "architecture", my guess would be Programmers. Just because we don't have tags for specific frameworks doesn't mean we won't take questions that involve them; odds are the only reason we don't have those tags and SO does is because SO is far bigger than us.
Design questions are most appropriate on Programmers.SE, however, keep the following in mind:
You must make sure your question is not too broad.
We are not going to design your app for you; you must outline what you've done so far, what you're looking to do, and the specific problem that you're having.
Please consider reading this post on Programmers Meta ...
Not every question has a place on the Stack Exchange network. However, questions can often be rephrased to fit the scope of a particular site.
For example, questions about the use of GitHub the web site might be a good fit for Web Applications:
Can GitHub handle commits that are older than GitHub?
What does the commit date on GitHub mean – is it the date ...
I certainly can't (and won't) speak to the specifics of the programmers site, but would offer an analogy that helps me know when and how to close and migrate a question on the site where I'm in a position to do that work.
I look it your question as "Is it a problem that the police are writing tickets against 30% of the drivers on road X last month?"
No - ...
If the question has to be a poll, it's not fit for Stack Exchange.
To prevent your question from being flagged and possibly removed, avoid asking subjective questions where …
there is no actual problem to be solved: “I’m curious if other people feel like I do.”
(UPDATE: It appears that the question has been amended from merely whether something should be flagged as non-constructive to include whether it should be eligible for migration. The answer below addressed the original question only.)
Much depends on how the question is framed rather than what is really be asked at its heart.
For example, ignoring the "...
I think you should just look at the FAQ's of both sites. Your questions is tagged with design patterns, which is covered in the FAQ of programmers.se, and doesn't really address a specific programming problem.
a site for professional programmers who are interested in getting expert answers on conceptual questions about software development....