We used to have "Too Localized" which read:
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the Internet. For help making this question more broadly applicable, see the FAQ.
It was good for gimme teh codez questions because the feature requested by the user would only help them, and so it fit there. At the time, this was a good fit for that type of question but was misused in other scenarios and so the reason was removed.
While I would personally like to see it reinstated, I doubt that we will go back to it. The current outlook is that if it requires writing a book or entire program to answer, then the question is too broad, so that is the close reason to use. As a result, questions asking for features have now gotten very specific in the demands for them.
"It needs to foo the bar, in the x situation, while being triggered from y; the output should be z". I see these daily, if not hourly. I vote to close them because they are simply requests for the community to do the work of others, and we are not a job shop. I have been fairly active on meta and am aware of the historical discussions that accompany these close reasons, so I don't find it counter-intuitive to choose the right reason.
However, many do find it counter-intuitive to find the right close reason in these cases and the end result is that the question remains open. In fact, it also means that if it is easier for a user to post an answer in only 5 minutes as opposed to reading 30 minutes of past discussion on the topic, they more than likely will post an answer and move on. Recently, this behavior has become the topic of taboo on meta here, and many are tired of seeing these types of low-quality questions receive answers.
While I am not sold on addressing this from an answer perspective retroactively, I believe that we can preemptively approach this situation by making it easier to close these questions. If it were easier to close the question, then there would be none of these answers.
Often users asking low-quality questions are asking for an actual feature to be created, or for an entire tutorial on how to solve their problem. When they include in their question something to the effect of "or direct me to one already available" it is very easy to close it as requesting an off-site resource. However, the on-site version is less obvious.
Here is an example of one, at the time of writing. It took glancing at the main site once to find. It was the first one I opened, https://stackoverflow.com/questions/33355790/how-to-assign-the-same-field-value-to-several-records-in-sqlite. It has clear issues and will probably be closed at some point in the near future because of increased awareness of it from informed users. In the wild though, it would probably have sat, no close votes, and garnered an answer or two effectively doing the work for them.
I propose that we make the "Too Broad" close reason more explicit in covering these types of questions so that experienced users can have clearer guidance on using this close reason.
Your question would receive too many long answers, would require users to create all the code, or write a tutorial. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.
