The difference between common developer and software engineer _ Classic Net Pick

Yesterday in the company received an internal mail, the Mail has a very interesting ppt, excerpt part of the common developer and software engineer differences:

Contrast 1:

A, general developers:

Master the basic knowledge of computer;

Familiar with computer resources, learned programming language, like to show off skills, like to compare the pros and cons of programming language;

To be able to compile a special function of the program is proud, do not understand the principle, superficial understanding;

Like personal development, do not attach importance to the preparation of documents;

B, software engineer:

Solid knowledge of basic computer;

Master more than two programming languages, rarely stay in the surface comparison programming language advantages and disadvantages;

Take pride in writing high-quality software that is user-satisfied.

Understand the pros and cons of personal development and team development, document specifications, complete.

Contrast 2:

A, general developers:

Only pay attention to the realization of the function, not heavy progress and quality assurance.

Afraid of being "tube" too dead, is apt to say that limited the idea, did not play space.

Do not like to do test work, think the test inferior, never done test work.

Only according to their own hobby learning technology;

B, software engineer:

Understand the balance between progress, quality (function) and cost.

The purpose of understanding norms is reuse, reuse is conducive to improve efficiency and focus on innovation.

Thinking that testing is more challenging than coding, you often do white-box testing for your companion's code.

According to the needs of enterprise projects and their own development goals in common choice of learning content and direction;

Contrast 3:

A, general developers:

Think other people's program is very poor, do not like to see other people's Code;

Always think that you understand the needs more than the business experts.

At the beginning of the project, like to say: "No problem, Soeasy."

Project greatly postponed, like to say: "The design is too bad, can't program."

B, software engineer:

Like to check the code for colleagues, and to gain the opportunity to learn the advantages of others;

Knowing yourself is probably more programming than a business expert.

At the beginning of the project, you like to ask: "What is that?" Why is that? ”。

When the project is greatly postponed, I like to say: "Why didn't I think of ..."?