Some qualities a good programmer must have

Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall

As a qualified and excellent programmer, what should be the quality? In fact, only six months of my work, seems to be far from qualified to talk about this topic, but this six months of growth so I benefited, in the programmer this topic can also more or less say a little valuable things to.

The necessary interest in development work

The interest is the best teacher, has certain interest to certain thing, only then can dive the heart to study, studies it, the work equally. If you are not interested in the work of the programmer, even if you are disgusted with it, then the results and ability of the work can be imagined. Here to say interest, does not require you to achieve the program has a fanatical hobby this degree, only need you still like this job can, even with the ordinary heart to face or not.

Ii. be good at learning and summarizing

All said that the programmer is a young rice to eat the occupation, although this remark is a little more absolute, but there are certain reasons. The technology in the IT field is changing too fast, a new language rise does not take too long time, only constantly contact and learn new things, can not be eliminated. The term "live and learn" is probably the most appropriate thing for programmers.

While learning, but also good at summing up. Each time a job is done, all of this work for a summary, such as what technology, how to carry out the project design, how to consider the user experience, and the problems arising in the work should be firmly remembered, from their own shortcomings to learn from, so as to enable themselves to grow up.

Third, to develop good habits

First of all, to have the habit of writing documents, do not feel that the programmer's work is just writing code, such a programmer lifetime is a "code farmers", absolutely no future. In the formal software company, the document status is very high, the development process often also reflects the location of the various links of documents. Software without documentation is difficult to survive for long, because there are more and more resistance in testing, reusing, and upgrading. The more advanced the programmer, the more attention should be paid to the document.

Second, develop good coding habits. What is the name of the variable? How is the function (method) named? How does the annotation in the program write? How is the indentation format of the program determined? A better company will have this documentation, but there are always programmers who never read the documents, and they think that the program written by the most talented programmers should have no one else to read, Then they really did it--the result is that others can not understand, unable to cooperate, to the end even they can not understand, such a person even as a programmer's basic qualities are not available. Write standardized, standardized program code, is a qualified programmer the most basic quality.

The last thing to mention is testing habits. Although formal software companies have specialized testing departments, the development sector cannot reduce their own demands. The sooner the software contains the problem, the lower the cost, and the more people and resources can be saved if the developer discovers some problems and solves it early in the development. At the same time, programmers should be the development of their own programs for functional testing, you always have to ensure that the software you develop the normal use of it? and to simulate as much as possible the user's actual use of some conditions, to think of some special abnormal conditions. Although it is difficult for developers to do a full range of tests in practice, it is important to understand the importance of this work.

Four, to be able to correctly understand user needs

Now everything is about a user experience, and this software is simply the survival of the fundamental. The user experience of a software can, to a great extent, determine the success of the software. Usually before the start of development work, the project team will analyze and discuss the user requirements of the project, correctly understand the user needs, then divide the reasonable module, even consider some potential threats, this is a good programmer has the quality. It is not easy to do this, such as my programmer, currently can only stay in the verbal, the actual work I think are very not comprehensive.

Pay attention to the reusability and modularization of the procedure

Have you always felt too tired to be a programmer? Yes, the programmer's job is really stressful, but some programmers work under pressure to add to themselves, and they're always doing repetitive work, never thinking about reusability and modularity. When a programmer completes a function module, it should not confine his thinking to this work, but should think about whether this part of the code can be detached from this work, can it be designed as a function module that other system could call? If everyone can have this kind of thinking, over the cumulative, everyone's repetitive work will be greatly reduced , there will be more energy for the development and innovation of new functions.

Vi. the spirit of teamwork

Although I put this point in the end, but its importance I do not need to put too much emphasis on it. Now the software features are often complex, but also involves a good UI (user interface), even considering the coordination of the whole system, a person is simply impossible to complete the work, so teamwork is necessary and must be. In a project team, how to distribute the work according to each person's area of expertise, how to coordinate human resources, is very important. And in the work encountered problems, the team should immediately find ways to help each other to solve.

About the professional qualities that a programmer must have, for the time being I only think so much. Although only six points, but can do that is really very good programmers, I believe this is not uncommon. The cultivation of these qualities takes a time, want to be unrealistic, but should be in the daily work to cultivate their own consciousness, and then gradually develop these qualities. I wish every programmer can get rid of the state of "code agriculture" and become a good programmer.

The article by the Nebula Blog original, the original address http://www.kaelli.com/27.html, reproduced please link form to indicate this address.