Revisions to Why was my question closed or down voted?

replaced http://softwareengineering.stackexchange.com/ with https://softwareengineering.stackexchange.com/

Source Link

edited Apr 13, 2017 at 12:45

Community Bot

1

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/

Source Link

edited Mar 20, 2017 at 10:29

Community Bot

1

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/

Source Link

edited Mar 17, 2017 at 10:37

Community Bot

1

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

#Too Broad#

The question you have asked either:

has too many possible answers
would require answers that are too long.

###Polling / Big List of Things###

Some questions are just polls for a design, or pattern, or name of a thing. If the accepted answer is based on "which answer I like best," rather than "which answer solves my problem," the question is probably a poll.

While some other Stack Exchanges allow it, Software Engineering SE frowns upon 'big list' type questions that seem to want to compile a list of things. Questions that fall into this category typically have the form of:

What are all the problems I will encounter with XYZ?
What are the pros and cons of XYZ?
How can XYZ be used?
Any ideas?

Questions like these don't pose a problem that can be solved by an answer. There is no definitive right answer that someone can go to, see the accepted answer and say "yep, that is the answer."

###Too long###

Can someone explain Java to me?

This question is too broad. There is far too much in Java to explain it to a person. While long and complete answers are a good thing, questions that would require books to answer completely don't make good questions.

Often these questions can be resolved by spending some time thinking about what the core problem is or what the first problem you are running into is.

###Related reading

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

If your motivation for asking the question is “I would like to participate in a discussion about ______”, then you should not be asking here.

Quick link: _{^{[Why was my question closed as "Too Broad?"](https://softwareengineering.meta.stackexchange.com/a/6490/)}}

replaced http://meta.softwareengineering.stackexchange.com/ with https://softwareengineering.meta.stackexchange.com/

Source Link

edited Mar 16, 2017 at 15:45

Community Bot

1

Loading

deleted 76 characters in body

Source Link

edited Nov 28, 2016 at 21:43

user22815

Loading

added 21 characters in body

Source Link

edited Feb 22, 2016 at 22:28

Robert Harvey

200.1k
3
35
76

Loading

deleted 16 characters in body

Source Link

edited Feb 22, 2016 at 22:15

Robert Harvey

200.1k
3
35
76

Loading

http://meta.programmers.stackexchange.com/questions/7537/why-do-some-examples-and-list-of-things-questions-get-closed

Source Link

edited Aug 25, 2015 at 22:54

gnat

20.8k
4
33
91

Loading

Post Made Community Wiki by ChrisFMod

occurred Jan 11, 2015 at 18:09

Add green field and blue sky

Source Link

edited Nov 2, 2014 at 4:14

user40980

Loading

too broad += (MSE) [Is a question that specifically asks for a summary of a broad topic valuable to Stack Exchange?](http://meta.stackexchange.com/questions/234642/is-a-question-that-specifically-asks-for-a-summary-of-a-broad-topic-valuable-to)

Source Link

edited Jul 31, 2014 at 0:56

gnat

20.8k
4
33
91

Loading

too broad += http://meta.programmers.stackexchange.com/questions/6629/how-do-i-explain-something-to-someone

Source Link

edited Apr 30, 2014 at 10:31

gnat

20.8k
4
33
91

Loading

added 2 characters in body

Source Link

edited Apr 17, 2014 at 17:30

Robert Harvey

200.1k
3
35
76

Loading

added 2 characters in body

Source Link

edited Apr 17, 2014 at 17:22

Robert Harvey

200.1k
3
35
76

Loading

MSO to MSE

Source Link

edited Apr 17, 2014 at 17:02

user40980

Loading

deleted 11 characters in body

Source Link

edited Apr 17, 2014 at 16:59

Robert Harvey

200.1k
3
35
76

Loading

'big list' type questions += http://meta.stackoverflow.com/tags/list-questions/info "see also: list-questions tag wiki at MSO"

Source Link

edited Apr 10, 2014 at 15:52

gnat

20.8k
4
33
91

Loading

Expand on polling

Source Link

edited Apr 10, 2014 at 15:24

user40980

Loading

added 133 characters in body

Source Link

edited Mar 9, 2014 at 0:05

user40980

Loading

Your questions should be reasonably scoped...

Source Link

edited Mar 6, 2014 at 6:21

gnat

20.8k
4
33
91

Loading

Source Link

created Feb 23, 2014 at 23:50

user40980

Loading

Stack Exchange Network

Return to Answer