Responsibility
Good leadership: A good leader always takes responsibility for the projects he is responsible for. If the project fails miserably, he knows he is to blame and has the courage to admit his mistake.
Bad leaders: Bad leaders don't think it's his fault, so he'll try to justify his team's failure, or put the blame on a few members of the team that he doesn't like.
work hard
Good leadership: Team leaders should be role models for team members. At the very least, he should work as hard as the rest of the team. Just because he's an authority doesn't mean he should only do the things he likes and leave other boring things to the team members to do.
Bad leaders: Bad leaders don't think that way, they feel like they shouldn't write code anymore, or keep other team members for what.
guide
Great Leaders: Great leaders always help junior engineers on the team. He will not let these junior engineers complete those tasks that are too difficult, because it is easy to cause the failure of the task or the result that cannot be completed smoothly. He knows that the investment in the team must pay off in the form of quality.
Bad leadership: Bad leaders don't care about that. Inexperienced team members should strengthen themselves through unusually complex tasks, regardless of the actual situation.
respect
Great Leaders: Great team leaders respect all team members, regardless of their experience. He knew there was only one way to lead a team, and that was through respect, not fear.
Bad leadership: A bad leader respects no one but himself. When someone made a mistake, he responded with all kinds of taunts and then reported it to higher management.
climb up
Good leaders: Good leaders believe in technology and expertise. He tries his best to do his job well and expects to get the reasonable position he expects.
Bad leaders: Bad leaders have little skill, but are good at flattering. On the one hand, he despised his subordinates, and on the other hand, he was infatuated with his superiors.
temper
优秀的领导：优秀的领导在感情上非常成熟，他知道如何控制自己的情绪。他不会对团队成员大吼大叫，或是威胁他们。
差劲的领导：差劲的领导喜欢炫耀自己的级别，如果不吓吓自己的团队他就没什么好办法。他认为恐惧是非常好的推动力。
信任
优秀的领导：优秀的领导非常信任自己的团队成员。他知道自己正与一群优秀的人一起工作，这也是他鼓励大家走出自己的知识舒适区的原因，因此团队成员最后都会学到很多，变得更强。
差劲的领导：差劲的领导不相信任何人，除了他自己。那些缺乏经验的开发者除了写文档外没资格做任何其他事情，或是只能为自己写的代码写一些单元测试而已。
任务分配
优秀的领导：优秀的领导选择那些其他人都不愿意做的任务，他向其他人做出了榜样，自己给自己分配了其他人都受够了的那些任务。
差劲的领导：差劲的领导总是选择自己最喜欢的任务。或许是自己想要尝试的新框架，他可不会将这个机会让给别人。不过，如果他发现太困难，那么就会将它交给团队其他成员来解决。
问题报告
优秀的领导：优秀的领导会尽自己所能来解决任何问题。不过有时这也是不够的，因此他会立刻向上级报告问题，接下来采取恰当的动作。
差劲的领导：差劲的领导总是掩饰问题。他不喜欢报告，因此这可能会影响到他的良好声誉。如果问题出现了，那么他就会找到责任人，因为他自己永远不可能出错。
代码审查
优秀的领导：优秀的领导深信代码审查的价值，鼓励团队参与到审查彼此工作的过程之中。当某个问题重复出现时，他会将其写到共享的知识博客中，这样每个人都能学习到解决问题的更好办法。
差劲的领导：差劲的领导根本没时间做代码审查，每个人都按照自己的方式工作。如果某人出现了问题，领导只是告诉他一声而已。
挫折
优秀的领导：优秀的领导上级可能是个差劲的领导，他告诉自己绝对不能成为像自己上级那样的人。他足够成熟，能够从他人的错误中学习。
差劲的领导：差劲的领导想让别人也经历自己还是初级工程师时所犯下的种种错误。
新想法
优秀的领导：优秀的领导更喜欢倾听而不是诉说。他会让所有的团队成员参与到头脑风暴中。他深知伟大的想法可能来自于你意想不到的地方。
差劲的领导：差劲的领导不喜欢其他人展示的所谓新想法。他的想法总是比其他人的好。如果他听到某个有趣的意见时，他可能对其嗤之以鼻，然后将其汇报给上级，说这个想法是自己想到的。