4 ms·
So, I don't feel the senior person in this case is necessarily wrong. So many languages give you 30 ways to do anything, it's key for a team to agree on standar
by axaxs 7y ago
So, I don't feel the senior person in this case is necessarily wrong. So many languages give you 30 ways to do anything, it's key for a team to agree on standards so that code is more easily read by everyone on the team. If you disagree about the style being suggested, don't argue back directly, but instead try to set up a quick chat with him/her and/or the team to suggest a different way of doing things. Having each member of a team having their own unique style gets annoying and confusing, to be honest.
As for conflict in general... communication. Be absolutely direct, but not confrontational. Do not be passive aggressive, or round a bout in your words. That's always worked for me, at least - not for getting my way, but getting clarification in the shortest time possible.
- bigiain 7y agoCompletely agree. What I'd do there would be make the change, then shoot off a quick message along the lines of: "Hey, I've made that change you suggested. A question though, I'm not sure I completely understand why you prefer it that way? Is it just a code style/consistency thing? Or is there something deeper I don't understand? If it's just style, do we have a style guide I should study? If not, would it be worth while me starting one as I learn these things along the way? Might help future new hires get up to speed quicker. I'd be happy to take that on if you think it's be useful?"