In my opinion, if the question is about a topic that's code related then, depending on the context, it's not at all unreasonable to expect the person who's asking the question to provide said code, or code snippets. The volume of questions being asked in this forum seems to have absolutely exploded of late. I don't think we have the luxury of "prying" that kind of information from people when they ask questions like when we were still in beta.
I'm coming to the view of, flag the post for closure if it's incomplete, unclear, etc., and users will be forced to learn "how to ask a qood question" before they receive their answer and the entire community will learn from observing.
When it comes to questions about things which don't include code, Airline pilots have been known for years in having their flight checklists they go through. In my view, understanding a "process" and making it "repeatable" is most definitely a key to solving any issues related to it. People often aren't taught how to think this way. It's something I learned in engineering school. There's a methodology to analysis that's more than sorting code. I've definitely no issues with asking someone how you can repeat the problem being described if they've not volunteered the info. They may not have a clue on where to begin attempting to do that themselves!
