avoid negativity and negative thinking. be pragmatic and realistic. ride the waves of passion and encourage passionate work, but also encourage balance and he

avoid negativity and negative thinking. be pragmatic and realistic. ride the waves of passion and encourage passionate work, but also encourage balance and health and try to be a leader in both regards, keeping your own work velocity up, but not getting burnt out it not taking care of yourself. learn your team and respect them. work at earning their respect. don't expect more work out of them than you put in. if you assign a dev 3 issues assign yourself 4. if that's not possible go out of your way to be transparent. developers are motivated by progress and want to see deliverables; so transparency about where you spend your time can help, especially at first. create an environment where it's ok to fail. both with software architecture and human challenges. avoid creating an environment where people can't communicate or ask for help. don't be passive aggressive, always be direct. be light hearted and have a soul, but don't get stuck being too nice and let that prevent you from being firm as needed. try to balance this out with letting people occasionally make their own mistakes and learning from them if it's in an area of the project that can afford to invest time in this learning. sometimes you can to force a good decision by being firm, but if you can let it evolve organically the person will feel they achieved more. try to do your best work and encourage that in others, but always calculate some buffer for things not always running at full tilt every day. good luck!