tl;dr - It's not as bad as it seems, most people coming to the site in this manner find themselves question blocked quickly, or (possibly) worse, depending on how many times they try to skirt the block.
Questions that state an odd set of constraints wrapped around what is typically a fairly simple problem aren't always bad. Back when we had a homework tag, I used to follow it because it was often applied to any seemingly beginner problem with odd twists. I very much enjoyed keeping myself sharp by working through solutions to these problems, especially ones that specified a certain maximum complexity. Interesting ones came in the form of "The GNU standard C library implements
strtok() and the re-entrant
strtok_r() as such, your job is to implement both without using (something)." You just knew there was a programmer on the other end of the line, by the 'dafok' overtone of the question alone.
Times have changed, and what used to be considered the bottom of the barrel is now something we'd breathe a sigh of relief at seeing - an actual programmer, someone interested in learning about the craft asking a question that isn't just solved by rudimentary skills. I'm eating every syllable of demonstrate a minimal understanding, while Shog is the one that put it in place, I came up with that particular disaster of a phrase. What I meant to say is this person isn't able to think about and solve problems like a programmer would, and that's not a good reason to shut down a question alone. I need to learn how not to think out loud. That's not an artifact of being a noob, that's an artifact of entering an industry where you're not likely to flourish. I'd never make it in ballet or on Broadway, but if that was the only way I had out of a bad situation, I'd probably at least try.
We tend to mirror the industry, we always have, and I'm not going to stop reminding people of that. The industry (especially in Android / IOS / PHP) is seeing a lot of people trying to get jobs within it that probably aren't ever going to be qualified. They may be able to memorize most of the standard library for some language, but they're not ever going to think like programmers because they aren't ever going to be programmers by the way in which we think of the craft today. They don't have natural talent, and the only nutcracker they'll ever dance in is a series of uncomfortable code reviews.
Angst around this is understandable, but a mirror can't fix things in what it shows - it just shows stuff (well, unless it's a magic mirror, but I'm restricted to one Hogwarts metaphor each month and I used mine weeks ago). I'm all for the "everyone should know something about how to code" movement, I think that's healthy and may lead some to discover talent that they wouldn't have otherwise. But, not everyone should be writing code for a living, just like you'd probably rather not see me in tights.
If you see aptitude in someone as evidenced by what they've put in their (please show me how to do (simple thing)) question, then take the opportunity to be a mentor and help elevate someone that can dance apart from those that just sort of wiggle and flop. If you don't see it, don't answer - use your votes as you see fit and move on to something more interesting. Don't worry about what other people answer, horrible questions are deleted quickly. Rewarded or not, some will just keep coming back and trying again and again and again until they get an answer - silence isn't going to (and doesn't) slow them down much.
Those that come to the site with that sort of expectation don't last long, and (if persistent enough with the same quality) find themselves unable to ask at all. I can't begin to tell you what you aren't seeing, it's pretty smelly.
But it's not specific to our community and what we're trying to build, it's .. sort of everywhere. I want the (salary/notoriety/both) of a programmer therefore I will become one is a far cry from I can't go to bed until this works - what you're seeing is the delta between the two.
Just be professional and polite, no matter what you do, because that's also a big part of what we're about.