In contrast, the manager just seems to be flailing around, unable to clarify. That is not correctable.
Only one of these people was ruining the interaction and thus needed advice.
And that's what I was responding to. I'm not going to respond to the manager because he's not reading this.
> your advice was that he should have replied to one "correct" interpretation that was not explicit.
No that was not my advice. I gave an example of a response which acknowledges the question, provides an answer "no", and gives the opportunity for the manager to come back with something if they really did have some valid case it might help. All in fewer words flailing about with a bunch of questions that still didn't answer the original.
My example remains valid even if the interpretation of the question and whether it matched the manager's intention was wrong, it still works.
The correctness I'm talking about is not in the answer to the technical question, it is how to go about having a polite interaction with others, which is what the author's stated goal was and what they got wrong.
> In contrast, the manager just seems to be flailing around, unable to clarify. That is not correctable.
I don't know what you mean by "not correctable". Correcting the behavior corrects it.
> Only one of these people was ruining the interaction and thus needed advice.
No, both do, and the manager isn't here, hence my comment.
I can definitely imagine a manager who might (unhelpfully) say "Should we rewrite in React?" to mean "I want the team to move to React for reasons I can't [or don't feel I have to] rigorously justify, I expect you to defer to me here, and now is your chance to alert me of big gotchas that we'll have to handle in the process".
Such a manager has failed to communicate what they actually want, and unless they can "correct" the listener to the desired interpretation, they're going to be frustrated when said listener takes their surface level meaning seriously. It sounds like that's what the OP was doing here (as the listener).