First, as Shog mentioned you can downvote it.
But in addition I often find these questions hard to answer, if not impossible. If I ask how to make an apple pie, and I don't indicate whether I know how to bake any kind of pie, or how to peel and slice apples, or even what an apple looks like (I might come back from the grocery store with carrots) you probably can't help me. You have no idea where to start. If the person doesn't appear to have chosen a programming language, an operating system, any frameworks, etc, how can you help them?
I vote to close these as Unclear What You're Asking and in my head I'm saying Unclear What Help You Need. Are you asking "please teach me C#, the concepts of database design, WPF, and how to architect a distributed system" or "why am I getting a null reference exception" ? I can't tell. So I can't answer. And questions that can't be answered should be closed.
If they've managed to provide enough information to make it clear what they want, then consider closing as Too Broad if what they want is "how do you build an ecommerce system?" or "I am writing my own operating system, how do I do that?" If they've written a clear crisp question whose answer would be of a reasonable length, and you can tell exactly what level of detail they need in that answer because you know what they already know and precisely what their problem is, but for some reason you feel they didn't try enough, well go ahead and just downvote. But I bet that never happens.
See also my answers to “first show your effort and then ask for help” comments and Do I have to write “I have tried” when I ask something?