The examples given are more about inexperience talking with skilled people and less about etiquette. Same thing happens when you directly talk to anyone else with deeper knowledge of any kind.
For anyone reading this that is not a dev just ask us what you're trying to accomplish without the formalities. If the dev throws a tantrum, they're still green and you should try to ask up the org chart if possible. Otherwise don't hesitate to ask the dev if there's someone who is a better fit for your question.
I do agree with the general idea behind this post though. We ask for brevity because we know, and you do too, that the conversation is going to be a long slog. We are not reassured by your formalities that this is going to be a clean one. Nobody likes to feel embarrassed or dumb. There's no way around this, just dive in please. I've been doing this for over a decade and I have been humbled many times by the broader business concerns I had no clue about. It happens.
For anyone reading this that is not a dev just ask us what you're trying to accomplish without the formalities. If the dev throws a tantrum, they're still green and you should try to ask up the org chart if possible. Otherwise don't hesitate to ask the dev if there's someone who is a better fit for your question.
I do agree with the general idea behind this post though. We ask for brevity because we know, and you do too, that the conversation is going to be a long slog. We are not reassured by your formalities that this is going to be a clean one. Nobody likes to feel embarrassed or dumb. There's no way around this, just dive in please. I've been doing this for over a decade and I have been humbled many times by the broader business concerns I had no clue about. It happens.