10 capabilities for a good software engineer (RPM)

mediocre people will always be mediocre, but good people are not the same! What are the similarities in this excellent framework? Of course, I heard that the following ten abilities, is bound to excellent engineers, "The Only Way"!

I. Ability to prepare for work

As the saying goes, "Spring, one day in the morning", the efficiency of a whole day, mainly depends on the morning work status. Then a good engineer comes to the company every morning and will certainly do this:

1. Take the initiative and greet the colleagues around you;

2. Organize your desk to keep the office environment clean and tidy;

3. Turn on the computer, take a glass of water, and use the time reasonably;

4. Open various communication contacts (so that the company can lead colleagues to facilitate contact);

5. Check out the main tasks today and start to finish it!

Second, the ability to do the right thing

We say that the product manager's goal is "to do the right thing," then the engineer's goal is to "do the right thing." The product manager is of course important, but engineers also influence the success or failure of the product. For engineers, the following links are very important:

1. When you receive the product manager's demand, we must communicate closely to ensure that there is no missing.

2. Think carefully and offer your own opinions and suggestions on products.

3. Fully understand the requirements, immediately design the solution, and actively find the technical supervisor to discuss the feasibility of the program;

4. Before tapping the code, first define the interface and the document, find the interface caller to confirm whether the interface is reasonable;

5. Each interface has a corresponding unit test, in order to ensure that the interface implementation changes, can immediately perform unit testing to determine whether the interface is stable;

6. The code should contain key annotations so that others can quickly understand the code logic through annotations;

7. Before delivery, self-test to ensure the stability of the integrated function;

8. After the product is released, record the code change log.

Iii. ability to work together with teammates

In the software development of this work, is very able to reflect the spirit of teamwork, want to become a good engineer must learn, to know how to work with partners, when an engineer lacks team consciousness, skill, then the result is not only for the team development disadvantage, and oneself will become more and more isolated, Here are some tips on how to improve your team spirit and ability to work together:

1. Be fully aware of your responsibilities and the responsibilities of your partners;

2. Do not doubt the ability of your partner;

3. Don't complain about anyone, help your partner to progress quickly;

4. Learn to praise others, let the partner feel full of positive energy;

5. Be a friend with a team partner.

Iv. ability to live happily with colleagues

In the eyes of many colleagues, the engineer is very quiet, eccentric personality, a mouth to talk about the love of offending, but as an engineer you do not know how to get along with other colleagues in harmony?

1. When speaking with other colleagues, be sure to smile, but also know how to think, can stand in each other's position to speak;

2. If a colleague wants you to do a little favor, whether he is busy as a dog or in a bad mood, be patient and listen to what they want you to help him.

3. When encountering the relevant business does not understand the time, the initiative to find understanding of colleagues, and very polite very polite to consult each other;

4. Often ask colleagues to go out to eat or participate in some activities in order to enhance the feelings between colleagues.

V. Ability to communicate with leaders

1. Do not take the leadership of the public to fart, as long as the leadership can feel the face of the good;

2. Able to accurately lead the real intentions, learn to stand on the position of the leadership to think about problems;

3. Timely report to the leadership, to be aware of the priorities of reporting;

4. Can help lead the management team, the team is treated as their own things;

5. Not ultra vires, not cross-level, and lead a growth and progress.

Vi. ability to learn new skills

Today's society, the Internet is a rapid development of the industry, and as an engineer, we will continue to learn new skills, to better with the times.

1. Learn about the features and what the technology can do through the skills-related website.

2. In accordance with the official website steps, oneself to do a so-and-so out, the purpose is to allow themselves to get started quickly, for later learning to do a good job;

3. Learn while doing hands, while taking notes;

4. Share your learning results and experience in the team, so that the whole team is full of learning atmosphere.

Seven, the ability to exercise product thinking

As a good engineer, not only the pursuit of technology, but also to understand the product. An engineer who does not understand the product is not a good engineer.

1. Train your own user perspective and treat yourself as a real user to feel the product;

2. Learn the business of the product;

3. Study competitor's products, and baizhanbudai the enemy;

4. Collect product data to make analysis and re-quantify products through data;

5. Understand industry trends.

Viii. ability to summarize work

No matter what you do, you have to finish, indifferent to engineers, not to mention, as a good engineer is absolutely not to hastily finish their daily work, there will be such a process: summary-introspection-to become excellent.

1. See what is not done on your day's tasks and why;

2. For the need to learn things, can be arranged to the weekend time;

3. Prepare the things for tomorrow and highlight what is preferred;

4. Learn to think and be good at thinking.

10 capabilities for a good software engineer (RPM)