Conceptual or specific?
I suggest you learn and ask about 'concepts', by applying them to and extrapolating them from specific problems:
For example you might ask, "Here is (a problem/situation), and I think I should use (concept) to solve this problem, but I don't understand (specific detail about applying the concept to the problem)?"
Or perhaps you could ask, "For (this problem), which of (either of these two concepts) should I use, and why?"
The FAQ says, "You should only ask practical, answerable questions based on actual problems that you face".
If I try to answer a theoretical question, I mightfind it difficult to know where to start, and when to stop. In contrast, when it's a practical question, it's easier (I can stop when I've said enough about the concept to solve the problem; I don't have to go on and try to say everything that might theoretically be said about the concept).
Also, text books (etc.) might better at explaining concepts. Whereas developers (Stack Overflow readers) might do better at applying concepts to specific problems (perhaps preferably, practical problems, though people will answer homework questions too).
I learn so much more when an experienced developer shares his paradigm?
I really don't know, what you're talking about: "shares his paradigm"?
Some specific examples (!!) would to help to explain/illustrate that.
Methodology, or just syntax and debugging help?
I sometimes like "software development process" questions: for example here or here.
I'm not sure where that fits on the conceptual-versus-specific continuum: maybe it's quite conceptual.