Return to Question

I wish to bring this question before the Code Review site. In the past, we have had this question: What makes a question too broad for code review?, which asks how to use the "Too Broad" close vote reason. It received one answer that said to use the Too Broad reason on comparative-review questions (which, BTW, have been determined to be on-topic for the site, so it is outdated).

Later, we have this question: How Broad is "Too Broad"?, which received answers about what makes a question too broad, and how to ask a good question.

My question is about whether we should use the "Too Broad" reason for the specific class of questions commonly known as "Gimme teh Codez." For example, we received this (now-deleted) question, which was closed with the following reason:

Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.

It also fits, nominally, into the following close reason, which is typically reserved for questions with working code behind a link:

Questions must include the code to be reviewed. Links to code hosted on third-party sites are permissible, but the most relevant excerpts must be embedded in the question itself.

We have 11 questions closed as "Too Broad". Should we be using the "Too Broad" close reason for such questions? Is the "Broken Code" close reason being used too broadly?

I wish to bring this question before the Code Review site. In the past, we have had this question: What makes a question too broad for code review?, which asks how to use the "Too Broad" close vote reason. It received one answer that said to use the Too Broad reason on comparative-review questions (which, BTW, have been determined to be on-topic for the site, so it is outdated).

Later, we have this question: How Broad is "Too Broad"?, which received answers about what makes a question too broad, and how to ask a good question.

My question is about whether we should use the "Too Broad" reason for the specific class of questions commonly known as "Gimme teh Codez." For example, we received this (now-deleted) question, which was closed with the following reason:

Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.

It also fits, nominally, into the following close reason, which is typically reserved for questions with working code behind a link:

Questions must include the code to be reviewed. Links to code hosted on third-party sites are permissible, but the most relevant excerpts must be embedded in the question itself.

We have 11 questions closed as "Too Broad". Should we be using the "Too Broad" close reason for such questions? Is the "Broken Code" close reason being used too broadly?

I wish to bring this question before the Code Review site. In the past, we have had this question: http://meta.codereview.stackexchange.com/questions/5364/what-makes-a-question-too-broad-for-code-review, which asks how to use the "Too Broad" close vote reason. It received one answer that said to use the Too Broad reason on comparative-review questions (which, BTW, have been determined to be on-topic for the site, so it is outdated).

Later, we have this question: http://meta.codereview.stackexchange.com/questions/6282/how-broad-is-too-broad, which received answers about what makes a question too broad, and how to ask a good question.

My question is about whether we should use the "Too Broad" reason for the specific class of questions commonly known as "Gimme teh Codez." For example, we received this (now-deleted) question, which was closed with the following reason:

Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.

It also fits, nominally, into the following close reason, which is typically reserved for questions with working code behind a link:

Questions must include the code to be reviewed. Links to code hosted on third-party sites are permissible, but the most relevant excerpts must be embedded in the question itself.

We have 11 questions closed as "Too Broad". Should we be using the "Too Broad" close reason for such questions? Is the "Broken Code" close reason being used too broadly?

I wish to bring this question before the Code Review site. In the past, we have had this question: What makes a question too broad for code review?, which asks how to use the "Too Broad" close vote reason. It received one answer that said to use the Too Broad reason on comparative-review questions (which, BTW, have been determined to be on-topic for the site, so it is outdated).

Later, we have this question: How Broad is "Too Broad"?, which received answers about what makes a question too broad, and how to ask a good question.

My question is about whether we should use the "Too Broad" reason for the specific class of questions commonly known as "Gimme teh Codez." For example, we received this (now-deleted) question, which was closed with the following reason:

Questions containing broken code or asking for advice about code not yet written are off-topic, as the code is not ready for review. After the question has been edited to contain working code, we will consider reopening it.

It also fits, nominally, into the following close reason, which is typically reserved for questions with working code behind a link:

Questions must include the code to be reviewed. Links to code hosted on third-party sites are permissible, but the most relevant excerpts must be embedded in the question itself.

We have 11 questions closed as "Too Broad". Should we be using the "Too Broad" close reason for such questions? Is the "Broken Code" close reason being used too broadly?