Thank you, Master. This is a very revealing topic. I now know what to do when the moment arrives. I eagerly await that moment.

I would like to add: "Automate as much as possible your agreements and standards" What we use is the editorconfig file to implement our code guidelines.

Thank you, I was hired as the only programmer of my company and I wasn't sure where to start.

Thank you, Tim! Nice question and the way you answer the question is great. I believe these type of questions and answers from expert like you is much needed nowadays. Keep going as always! 👍

Dang you're a wise man. Such a calming common sense video. Love it Tim.

What a great topic, it's always good to hear your thoughts on subjects around real world dev stuff. Couldn't agree more with the don't make it a democracy bit hehe. Get two devs together and ask the wrong question and you'll always get an argument :) When I've done this with teams before I like to start with a context. So my first task is to review the code and check for the level of consistency that's there and if there are inconsistencies you want to get resolve start with an agreement from the team that getting rid of them, without saying how, is a good idea, at least that way you should be able to at least start with an agreement before the preferences kick in. Also can highly recommend your advice on explaining that just having a preference isn't a good enough reason to go one way or another, you need a reason. This is another thing you can get agreement on most times :) Love your work Tim!

This has been hashed for years at least since 1994 when i started in this industry. The industry has progressed to more universal standards which is a good thing. These questions still remain. I had a boss once say be consistent even if it's wrong, consistency establishes a baseline to work off of, if everything everyday is done different going to be hard to adjust.

Thanks Tim 🙂as always was great and helpful 👌

Under-rated video.

I need to know the best practices so that code that works is not rejected in PRs due to ‘opinions’ or ‘common sense’

It is already too general. No benefit for me and our team. Could you be more specific? For example, please say 10 yours concrete simple rules with explanations why these rules are very important for cooperation in the team.