Coding style is and will always be argumentative. It’s like the whole tab vs space on the show Silicon Valley.
Your team has to decide on coding standards, either those used by industry references or those decided internally.
I see so much code where I personally disagree with the style, bring approaches from other languages due to misunderstanding or habits, that does not make it wrong, just not they way someone else would do it.
3 core things, IMHO:
- readability (if they can't follow your stuff, then they will just re-write it. How long are you code lines? Are you using a bunch of shorthand, alias craziness that no one can follow or even know? )
- maintainability (Can anyone who follows you deal with it without undue stress and strain? When I see your code, can I be assured that it will be reusable?)
- consistency (When I see your code, is the following a standard or are you doing your code the same way, all the time?)
Many will argue about / for one way or the other, but if they don’t manage / pay you, work with you or collaborate with you, then it’s just their opinion that you personally have to accept, reject or take the parts the make since to your own style and deliveries.
There are times when bracing, bracketing, parenthetical, quoting, etc., will only work if they are done a certain way depending on what you are doing and what the language restrictions /confines are.