22 remove some verbiage (from the first half of the answer) to improve readability
source | link

A good question on Software Engineering Stack Exchange (previously known as Programmers) would beFor a start, a good question on Stack Overflow. This isn't to say that if it is on topic:

  • not too broad
  • not opinion polling
  • and not unclear.

If you'd close a question on Stack Overflow then it is on topic here. Rather that it's not too broad, not opinion polling, and not unclear. If you have the slightest inkling of closing the question for anyone of thosethese reasons, don't suggest posting it here on Software Engineering.SE. Those

Those close reasons span all of the Stack Exchange network.

Suggesting to someone to repost a question that is too broad or primary opinion would get it closed on Software Engineering.SE too and that's really something we'd rather avoid. It is no fun to getFor a question bounced from one site to another and being told repeatedly we don't want it here. If it needs to be fixed, it needs to be fixed before it is reposteddescription or telling the OP exactly what needs to be fixed.

The interpretation of thesethe close reasons is described in, which are specific to this Software Engineering SE site, see Why was my question closed or down voted? which may have a bit higher of a bar in some aspects than Stack Overflow. This meta question also goes into the off topic reasons for the site.

 

Some commonly referredWhat are common types of poor questionsquestion?

I"I don't understand..."

Here's"Here's my problem. Anyone have a solution?"

A"A blog I read said..."

 

So what is in scope here? I thought it was everything "not programming related"...

While we have some of the legacy of "not programming related" still hanging over us, theThe help center is likely the best spot to read for our scope:i.e. What topics can I ask about here? is the best page to read for our scope:

So what questions do you want?

WellWhat we want are well thought out and researched questions about the Software Development Life Cycle that aren't code troubleshooting questions. Remember

Remember that algorithm questions are also on topic on Stack Overflow (so you don't need to migrate those).

 
 

A good question on Software Engineering Stack Exchange (previously known as Programmers) would be a good question on Stack Overflow. This isn't to say that if it is on topic on Stack Overflow then it is on topic here. Rather that it's not too broad, not opinion polling, and not unclear. If you have the slightest inkling of closing the question for any of those reasons, don't suggest Software Engineering.SE. Those reasons span all of the Stack Exchange network.

Suggesting to someone to repost a question that is too broad or primary opinion would get it closed on Software Engineering.SE too and that's really something we'd rather avoid. It is no fun to get a question bounced from one site to another and being told repeatedly we don't want it here. If it needs to be fixed, it needs to be fixed before it is reposted or telling the OP exactly what needs to be fixed.

The interpretation of these close reasons is described in Why was my question closed or down voted? which may have a bit higher of a bar in some aspects than Stack Overflow. This meta question also goes into the off topic reasons for the site.

Some commonly referred poor questions

I don't understand...

Here's my problem. Anyone have a solution?

A blog I read said...

So what is in scope here? I thought it was everything "not programming related"...

While we have some of the legacy of "not programming related" still hanging over us, the help center is likely the best spot to read for our scope: What topics can I ask about here?

So what questions do you want?

Well thought out and researched questions about the Software Development Life Cycle that aren't code troubleshooting questions. Remember that algorithm questions are also on topic on Stack Overflow (so you don't need to migrate those).

For a start, a good question is:

  • not too broad
  • not opinion polling
  • and not unclear.

If you'd close a question on Stack Overflow for one of these reasons, don't suggest posting it here on Software Engineering.SE.

Those close reasons span all of the Stack Exchange network.

For a description or interpretation of the close reasons, which are specific to this Software Engineering SE site, see Why was my question closed or down voted?

 

What are common types of poor question?

"I don't understand..."

"Here's my problem. Anyone have a solution?"

"A blog I read said..."

 

So what is in scope here?

The help center i.e. What topics can I ask about here? is the best page to read for our scope:

What we want are well thought out and researched questions about the Software Development Life Cycle that aren't code troubleshooting questions.

Remember that algorithm questions are also on topic on Stack Overflow (so you don't need to migrate those).

 
 
21 [Edit removed during grace period]
source | link
20 replaced http://softwareengineering.stackexchange.com/ with https://softwareengineering.stackexchange.com/
source | link

While we have some of the legacy of "not programming related" still hanging over us, the help center is likely the best spot to read for our scope: What topics can I ask about here?What topics can I ask about here?

While we have some of the legacy of "not programming related" still hanging over us, the help center is likely the best spot to read for our scope: What topics can I ask about here?

While we have some of the legacy of "not programming related" still hanging over us, the help center is likely the best spot to read for our scope: What topics can I ask about here?

19 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link
18 replaced http://meta.programmers.stackexchange.com/ with https://softwareengineering.meta.stackexchange.com/
source | link
17 replaced http://meta.programmers.stackexchange.com/ with https://softwareengineering.meta.stackexchange.com/
source | link
16 replaced http://meta.programmers.stackexchange.com/ with https://softwareengineering.meta.stackexchange.com/
source | link
15 replaced http://meta.softwareengineering.stackexchange.com/ with https://softwareengineering.meta.stackexchange.com/
source | link
14 http://meta.softwareengineering.stackexchange.com/questions/tagged/new-site-name
source | link
13 deleted 642 characters in body
source | link
12 you don't need to migrate those += https://blog.stackoverflow.com/2012/03/respect-the-community-your-own-and-others/ "'Be a bit jealous of your site - don't blithely turn askers away simply because their question could be asked somewhere else...'"
source | link
11 minor typo corrected
source | link
10 Tweak descriptions and links to list of off topic reasons.
source | link
9 Expanded "tool" to "tool, library, other..." to match the close reason more accurately.
source | link
8 Added link to the licensing faq
source | link
7 added 501 characters in body
source | link
6 legal advice += http://programmers.stackexchange.com/help/on-topic
source | link
5 For a more detailed outline of what is generally expected at Programmers, see http://meta.programmers.stackexchange.com/questions/6559/why-is-research-important
source | link
4 Increase header size. Call out common poor question types.
source | link
3 "post this on Programmers.SE" comments += http://meta.programmers.stackexchange.com/q/7154/31260 "we even had to introduce a chat bot for identifying when Programmers is mentioned on Stack Overflow"
source | link
2 There is an expectation += http://meta.stackexchange.com/a/234663/165773
source | link
1
source | link