the anti-pattern opinion seems to come from a lack of understanding of our tools
It's 100% okay to disagree, but it also matters how you disagree. Saying something like that undermines a more senior dev's experience by claiming they lack an understanding of the tools they've been working with.
Yeah I think this might come across poorly 🤔 So how would you claim that a more senior dev's understanding of their tools has a gap, without making them feel undermined? (Not assuming the OP is right or wrong here, just brainstorming better ways for them to voice that feedback)
The "asking why" approach that others are suggesting might be good here. So instead of just stating their opinion is misguided, maybe asking Dev leading questions based on your own understanding to encourage deeper thoughts from everyone, and see if they come to the same conclusion as you.
I think any dev worth their salt should be eager to revise an opinion in the face of better understanding, but also able to articulate their position effectively to more junior devs so they can learn from you.
I definitely would not have said this:
It's 100% okay to disagree, but it also matters how you disagree. Saying something like that undermines a more senior dev's experience by claiming they lack an understanding of the tools they've been working with.
100% agree, it's all about the way you communicate something. Saying "a lack of understanding" is negative phrasing, that's something to be avoided.
Yeah I think this might come across poorly 🤔 So how would you claim that a more senior dev's understanding of their tools has a gap, without making them feel undermined? (Not assuming the OP is right or wrong here, just brainstorming better ways for them to voice that feedback)
The "asking why" approach that others are suggesting might be good here. So instead of just stating their opinion is misguided, maybe asking Dev leading questions based on your own understanding to encourage deeper thoughts from everyone, and see if they come to the same conclusion as you.
I think any dev worth their salt should be eager to revise an opinion in the face of better understanding, but also able to articulate their position effectively to more junior devs so they can learn from you.
Basically, I'd say exactly what OP was thinking, but without implying that the senior dev misunderstands the tools they work with.