|
|
|
|
|
by Beltalowda
1406 days ago
|
|
It's hard to explain, but as a first response it implies "the current code is fine", or "we don't need to do this". That is, you risk it being perceived as a challenge to the idea ("rewrite it in React"), rather than a question to explore the goals. Note that I wouldn't mind such a question at all myself, but others can be more sensitive to such things. Actually, I think "Why? Is the current code not working?" is a perfectly valid engineering question for rewriting or refactoring anything, but not everyone has this kind of engineering mindset. I would phrase it more open-ended, such as "Okay! What goals would you like to achieve?" |
|
I understand from the comments and my life experience that there is something there, I learned to smile, be engaging, mirror body posture, ask questions instead of going into statements too quickly, but what are you describing just makes no sense to me. How is "what goals would you like to achieve?" not dismissive, but "do you think our checkout is not performing well?" is?
One is a pretty vague question about something they already stated (they want to ask me my opinion about rewriting the checkout in react because company X improved their checkout), the other one is something I need input on to be able to do that. It's literally the most efficient question I can think of so that I can avoid wasting their time.
I described in another comment how it never "really" occurred to me that a question could be perceived as dismissive. If I wanted to dismissive I would... just say so?
The thing is, saying it is dismissive, getting upset, and shutting me down helps exactly no one here. What could help is to realize I am not actually trying to be dismissive, point out that my question might be interpreted as such, and then move on. Trust me that I don't let this kind of advice go to waste.