I often see questions with huge amounts of source code and very small amounts of accompanying content that essentially amount to, "here is a large script, please debug it for me." (this is a recent example). I dread these posts because to do a full code review would take hours and require a lot of information-gathering from the user, and I seldom see someone putting in the time to help someone do their job on a task they don't seem to be able to break up into smaller pieces.
If the same amount of information or the same requirements were applied to a question without such a large amount of code, it would very quickly be closed as too broad or too specific, and quite often these questions go incompletely answered or linger with no accepted answer for quite some time.
Do we have a policy for this? With content this long and nonspecific outside of a
code block we'd ask the user to cut their post up into multiple, smaller questions or clarify what they are asking for. We're not doing that for these script questions, should we start applying an existing policy to them more vigorously or clarify/add policy to keep up the quality of the site? Additionally, should we just start directing these sort of thing to something like the Code Review Stack Exchange if they're more about programming than GIS?