How to be the head of the development team---manage others first, please start as a qualified programmer

Development Manager (Development team leader) the development manager is the master of the team. That should be the role model for the whole team work, whether it is working efficiency, attitude, analysis and design level, business knowledge, technical ability in all aspects must strive to become team members role models.In addition to arranging the current work, the development manager needs to actively learn and constantly improve his business and technical level. Many people will say that very busy without time, that requires the development manager to pay more effort than others, because the development manager to pay higher than others, should pay more, for the company to create higher value. If I am the boss, I will pay you a raise, not only for your previous work, but more importantly, expect you to have higher output later, so from the developer to the development manager, you have to work harder to have higher output.key issues and core code must be done as much as you can. By addressing key issues, you can establish your own image and authority in the minds of your team members, reduce the error of post-workload estimates, and reduce the risk of changes in team members, and the development manager is ready to be a substitute for anyone on the team. Developers with statistically excellent open source software code more than 70% are more than 30-year-olds, most of our development managers are younger than this, and a good programmer needs at least 10 years to be able to practice. If you do not start now, only a few people, I think the company is a waste of resources, for the individual is lost opportunities for growth. Now the whole industry people are very impetuous important reason is that most programmers overestimate their own ability level, reduce the requirements of their own standards, many people work for many years, even a qualified programmer is not, not to mention good programmers. Do not think that coding is a kind of low-level labor, we must correct this erroneous thinking, a lot of master-level characters are writing code, not to mention that they are just a unqualified programmer.arrange work, the first tight after the loose principle, do things must first tight, arrange work to be first tight, to self and team members to make mistakes and solve the risk of time, leave sufficient margin. Arrange tasks to pressure the team members, to the standard of self-completed tasks to ask subordinates. summarize the competency characteristics of your own and outstanding members and copy them to other team members. Copying is the ability to do the job, to do things and to think about the problem, not just to tell him how to do a specific thing. Check the output of team members in time, understand the characteristics and ability level of members through checking the output of members, and point out the deficiencies in time. So as to be able to arrange the work tasks according to the personnel ability characteristic. To point out the inadequacy of the members is to be personally responsible for him.positive thoughts go down, negative thoughts to upload, negative thoughts and problems can only be reflected in the superior leadership, do not show up in front of subordinates, bring to subordinates is always positive thoughts. It is difficult for most people to accept the idea that the team members should have a positive thought and seize the usual opportunities, and not just wait to talk in person. Try to instill positive thoughts for the sake of each other, and don't always act like a leader in giving orders.