As someone that has no experience with the role at all, but had to deal with some… special people, I feel the first three cannot be overstated. Your job will b

As someone that has no experience with the role at all, but had to deal with some… special people, I feel the first three cannot be overstated. Your job will be more one of herding people into doing things the right way, and it should never be one of you doing all the interesting decision making or prescribing the whole structure from the get go. Talk with people, make sure they are invested in the overall architecture as well. And don't assume someone didn't think it through on their own until you discussed their ideas. People who do all the architecture planning themselves, even if they aren't butting heads with anyone, can have a really negative impact on the team as a whole, because all other team members stop worrying about the topic and just let the other guy do it. I already had to deal with outcomes of this; code that has been written by "drones" is nothing you want to work with.