Cultivation of excellent employees-the road to experts and Management

(1) Good employee Quality

There are many types of good employees. Try to abstract a definition --A good employee is the person in charge who gives his/her tasks peace of mind, and his/her colleagues who like to work with him, take responsibility for his/her own work, aim for self-improvement, and realize value.In the era of knowledge economy, good employees must first manage themselves and ultimately be able to stand alone. (For more information, see "how to cultivate the ability to stand alone" in the blog post "). As half a programmer, let's have a chat about the qualities that employees should possess (some for programmers ).

I think,A good employee must be measured by skill level (Technical width, breadth, and proficiency), communication skills, work attitude, and learning ability.For example, to be a good programmer, whether it is intended for management or senior engineers, Lu Qiming @ happydeer should say "Start with a high-performance programmer ", the best developer is often not the one who writes the most code and the fastest (one of the top programmers),People with excellent communication skills, starting from the overall situation, capable of thinking and looking at them from a higher perspective.A good employee's work style should include (but not limited ):

(1) know what you are doing and what you want to do. They have to prioritize their jobs, that is, they know how to manage time.

(2) reassure supervisors and colleagues. They are guided by solving problems and can always complete their tasks on time and on demand. They don't complain, they always reflect on themselves, and they try to solve their own problems first.

(3) Be aware of the overall situation. They grasp the overall structure of the system and examine the task from a higher perspective. They follow the root principle and never rely on luck programming. They will never modify the code to solve the bug, instead, investigate the root cause of the bug as much as possible.

(4) put the team first. They can get along well with others, they choose to cooperate, they can recognize the excellence of others, and appreciate.

(5) high standards and strict requirements on yourself. They constantly improve their technical capabilities and personal accomplishments, and help others make progress together.

(6) excellent communication and presentation skills. They communicate with people clearly, effectively, and appropriately, persuade others to collaborate with them, and push forward the project. (2) work attitude and skills

(1) both parties should reach a full consensus on accepting and assigning tasks. To minimize understanding errors, when assigning tasks to a supervisor, you need to determine with the supervisor what the task is, who is involved, what the goal is achieved, when the task is completed, and what the measurement standards are.

(2) Report the work plan and progress. Supervisors need to grasp the overall situation, so they need to be in the state of "everything is under control. As an employee, you must report the task plan and report the progress in stages after reaching a consensus on the task. The progress report includes what goals are achieved within the specified period, what problems are solved, and how you use them. In this way, you have gained a lot from yourself.

(3) The task should be accepted unconditionally, communicated proactively, and not complained in particular. The supervisor is not a fool and won't hit your head for no reason. If you are too busy or do not understand at this time, tell the supervisor truthfully, indicate the difficulty, ask the supervisor to decide whether to submit the decision to others or delay the decision. This requires you to manage your personal time first.

(4) do not ask the supervisor what to do. You are employed to solve the problem. You should be an expert, at least on the road to being an expert. When you encounter an unknown problem, you can think and consult yourself to give your understanding and multiple solutions for your supervisor to choose.

(5) take the initiative to take responsibilities and share tasks. The supervisor is actually very tired, especially the technical director. Do you look at him as inconsiderate and distressed? You must take the initiative to promote your work and report it. This requires your global awareness and a higher perspective. (3) What can be done in idle time

Idle period indicates that the project enters the test phase, the end of one project, and the other has not started. Managers should pay attention to the idle period and help members arrange improvement plans. Individuals should be responsible for themselves and contribute to the team. Tasks that can be done (but are not limited to) in the idle period include:

(1) analyzing previous bugs can analyze the causes and rules of bugs, or develop tools to help you check and analyze bugs. It is a unremitting effort to automate everything possible.

(2) sum up experience to improve the level of personal skills. The conclusion should be carried out from a higher perspective: Why? How can upstream and downstream modules collaborate? What is a better alternative? Writing and sharing are a good way to sum up. Writing is a process of organizing your own ideas, organizing your knowledge system, discovering and filling in vulnerabilities. It is one of the best ways to improve your skills and make your thoughts clearer. Effective Writing is a basic skill and a career boost.

(3) reflect on your career. Various talents are required in software projects, this includes product managers who analyze requirements and propose solutions, project management who manage and coordinate project stakeholders, architects who design architectures, programmers who code and study algorithms, etc. We should plan our career based on our character characteristics. Idle Time is the ideal time to review your current career situation. Were you correct about yourself? Are you in your ideal position now? Is your career moving in the right direction? Are you ready to meet new challenges? What do you need to do to keep yourself busy and passionate? If you think you have to change it, the sooner you take action, the better.

(4) learn new knowledge and new skills. Learn the knowledge that a team may use in the future or that they are interested in. In this way, they can increase their knowledge and skills to improve their competitiveness. In addition, they can reserve technology and promote the team.

(5) team building, technical experience accumulation, and collaboration promotion. This requires the promotion of the supervisor to review the technical and management experience in the past project development process. What are common mistakes? What are the mistakes made by the team? How can we do better? How can we achieve better cooperation?

(6) prototype development: Prototype the team's development experience and ideas for analysis and learning. You can also learn user requirements, plan future products, and study related new skills in advance.

Reprinted link: http://blog.csdn.net/suipingsp/article/details/36643517