I hate these typical questions which hiring managers or candidates ask each other with no real meaning behind. E.g. "how do you use source control"? What is t

I hate these typical questions which hiring managers or candidates ask each other with no real meaning behind. E.g. "how do you use source control"? What is the intention of this question. What value do I gain from this question? It implies that I have a specific way of interacting with source control in mind and if they don't follow the say way then I'm unhappy or what? Interviews take such a long time, I am of the opinion that I only want to ask questions which genuinly help me later to make a decision. e.g. instead of "what tech do you usually use?" I'd ask "I've been recently playing with X and think it's a brilliant use case for doing Y. If I were on your team and I'd want to do Y with X, would that be an option, or what's the protocol in tech decisions in your team?" With a concrete question like this the interviewer has to explain to me how they actually decide on tech and give me a more or less yes/no answer to whether what I want would be possible. I find this a lot better than a generic tech question and then get bombarded with a ton of buzz words which don't really say much about how open the tech teams are to picking their own tools for the job, etc.