Now, admittedly, it's very tone dependent. "Why don't you X" can be asked humbly and with a truly inquisitive tone, or with a sneering tone whose obvious implication is that you must be either ignorant of X or too dumb to see its merits. But in writing, at least, I try to infer the more charitable attitude of genuine curiosity.
I've also say through Q&A sessions where a guy got up to the microphone to recommend books for the guy giving the presentation to read. It was uncomfortable.
Also, if you want to understand why someone did Y, ask deeper questions around why they did Y, don't ask why they didn't pick the other 500,000 possible solutions.
Firstly, and sadly, I get a bit mentally stuck on X. Secondly I assume I have missed something. Whatever I have missed is probably quite important, since otherwise X was a good choice.
Both of these effects mean that I will probably learn a lot from knowing why someone decided not to do X. So, if I've been mulling the question for a while, and can't get an answer, I think it makes perfect sense to ask "why didn't you do X". After all, that is exactly what I am wondering in good faith.
It sucks that the question is often used sarcastically, because to me it's a very useful question for understanding someone else's process.
Often I've asked it because I privately thought "why didn't they use X?", but I'm seldom actually interested in hearing why they didn't.
But ROS is indeed a popular framework for robotics, so the question is a reasonable one to ask.
But yes, I also try to interpret it charitably as well too. I just also try to make my own curiosity clear on the flip side.
There's a whole thing called nonviolent communication and the basic premise is that if you spin someone up by choosing your words poorly, that's as much on you as it is on them.
That said, sometimes even the most skilled communicator might find themselves spining someone up despite their best efforts. At the end of the day all we have is self awareness and good intent, but if the other person is hell bent on being oppositional, that's gonna be very hard to navigate.
Because even if you exclude the concern trolls who aren't actually interested in your answer, just fighting with you, it is a never-ending stream of people who want to bikeshed your choices devoid of the context that makes it worth even trying to answer.
Life is too short.
That being said, I love being challenged. Also by people new or un experienced in my field. Because it's an opportunity to learn. Either because I missed something (naive questions are really great for that), because I have to voice my thoughts and explain my thought process (and discover flaws in it), because the person asking is way better in what ever we are talking about,... you name it. Being challenged just because definitely isn't part of that.
What tone do you want?
I'm extremely confused, and I don't understand your implication that an inquisitive tone won't be respectful or polite.
(And when it is curiosity, it's less offensive from someone that doesn't know much, which is part of what threw me off so badly.)
As the running joke on the TV series goes "Phrasing". Phrasing is the key difference, especially in a textual medium. As you point out, it's the tone.
I've seen "Why don't you do X" phrased in a variety of ways, and the best phrasing I've found seen was along the lines of "I would normally do X in the scenario you've described, but Y was obviously better for your use case, would you mind sharing why?"
The worst possible phrasing of "Why don't you do X" is "Why would you even consider Y, everyone competent knows X is how you do it".
...and then it turns out that actually, Y was the best way to approach the given use case, X wasn't suitable, and now someone looks like a bit of a dick.
There are multiple assumptions in that question that could make it crash and burn really badly. What if they actually didn't consider X? What if they do think Y is better, and X is interim? What if they had a lazy reason to prefer Y, and interpret the hyping up of the quality of their decision as calling them out?
As opposed to assuming they're cousin loving inbreds who did Y because they hate every computer scientist ever.
Assuming that doing Y was indeed wrong, and you want to correct that... do you think approaching it with the mindset of "you're a competent person who made the best choice you could see" is going to work better or worse than approaching out as "you're so incompetent, I've met more capable toasters, and you obviously did this because you hate America"?
It's just people skills, my friend. Start your disagreements by assuming the best of your opponent.
And why is this an "opponent"?
How about both not being rude and trying to minimize assumptions?
Consider that they probably looked at X, but don't put them into an extremely awkward position if they didn't. And the same for the other things I pointed out.
It's just people skills, my friend.
This lead to the pathological condition whereby adding engineers to the team slowed progress, as it simply created more values for x.
If you piss off enough people over the course of a 6 month to a year project, it's unlikely that the perception of even a game changing win will be positive. As most large companies base promotions off of feedback, pissing off the wrong people will also block development.
When you see tenured members of a team exhibiting certain behaviors, it's often due to those behaviors optimally solving for the incentives of the organization.
The question of that form is akin to “proving a negative”
I think the premise of the article is dealing more with random drive-by comments where the person is really just advertising x, rather than being genuinely curious.
However it's a great question to understand why certain decisions were made. The best engineers know that most of the work gets done in the planning and decision-making, not by stubbornly diving into something. If it was really the best decision at the time then the merits should stand the test, otherwise the defensiveness to answer is far more suspect than an innocent question.
Asking why you did something is a reasonable question. Asking why you did not do something tends know-it-all and/or help-vampire territory.
Instead of assuming the asker is a "know-it-all", what if they actually do know more? I've learned more from counter arguments (both hearing and making them) in all aspects of engineering and life in general.
I'll never turn down such a question and actively engage them because it makes me aware of alternatives at the very least, and often helps in future decisions. There are plenty of stories posted on HN of poor decisions that probably could've been avoided if someone considered some alternatives.
"Why don't you use Reaper?"
"Why not Bitwig?"
"Why not Linux?"
"Why not Ardour?"
"Why not LMMS?"
(the answer is "I spent tens to thousands of hours in each and they all feel like a regression next to Ableton Live and my very stable and productive Windows 11 Pro install")
This is music, but from this thread it sounds like it's the case with most fields. It's always the Standard Alternative Suggestions that assume the askee is an absolute novice who wouldn't be aware of and wouldn't have extensive experience trying or at least considering the entire space of possibilities before settling on a path.
"Why do you assume the asker is a know-it-all?"
Experience. It's cool that you have a different experience where it's not a waste of time.
Personally, I always get that feeling of fright plus eagerness. "Oh god, have we wasted our time" plus "Oh man, can we save so much more?". And you only have to explain to coworkers once anyway. They'll either demonstrate their idea is better or turn into additional broadcasters for the viewpoint.
The pithy answer is because of all the things in the world that someone might propose need doing, I can only do a vanishingly tiny fraction of them. Even the largest, most profitable company in the world can only do a slightly larger tiny fraction of them.
The reason we don't do the things you ask about is because we are focused on doing the things which we've prioritized using our best judgement. The idea that we somehow owe an explanation to internet randos about everything we don't do is indicative of a personality that must not be allowed anywhere near engineers with work to do.