Thanks for the response. I do agree to all of these suggestions, and honestly we can't just make up hypothetical scenario after hypothetical scenario of what the best way to phrase things are. It depends so much on me, the manager, the time of day, the team culture.
I think my point in the article is to say:
I am autistic, and I might not communicate the way you are expecting. If I am asking questions, it is for what I think is a good reason. What I am not doing is rejecting your question and not acknowledging I am wrong. If I wanted to reject your opinion, I would reject it, not mess around asking oblique questions.
It's great that everybody seems to think this is my problem alone to solve, and I'm somehow doing this on purpose. I am not, I am trying very hard to get better, part of which is to share my experiences. Yet, that also seems to be criticized ("who puts so much effort into analyzing these situations?").
I have very productive relationships with other engineers and product managers and business owners, so clearly this can work out just well, but that's not what I wanted to cover here. I will in the future however, and I covered a tiny aspect of "digging deep into business questions, as an engineer" here: https://dev.to/wesen/worse-ux-for-a-better-product-how-to-th...
I think my point in the article is to say:
I am autistic, and I might not communicate the way you are expecting. If I am asking questions, it is for what I think is a good reason. What I am not doing is rejecting your question and not acknowledging I am wrong. If I wanted to reject your opinion, I would reject it, not mess around asking oblique questions.
It's great that everybody seems to think this is my problem alone to solve, and I'm somehow doing this on purpose. I am not, I am trying very hard to get better, part of which is to share my experiences. Yet, that also seems to be criticized ("who puts so much effort into analyzing these situations?").
I have very productive relationships with other engineers and product managers and business owners, so clearly this can work out just well, but that's not what I wanted to cover here. I will in the future however, and I covered a tiny aspect of "digging deep into business questions, as an engineer" here: https://dev.to/wesen/worse-ux-for-a-better-product-how-to-th...