How to improve the programmer's "performance"

Programmers are often obsessed with optimizing the performance of the program, and we will always focus on some of the brain-racking optimization recommendations, such as how to simplify the code, how to improve the speed of the software, how to improve software stability, and so on. This article discusses some of the suggestions that programmers can take to optimize their "performance".

1. Improve the ability of document writing

Lack of documentation, software development is fatal, on the one hand, the software does not have retrospective ability to find the origin of software development, thinking, on the other hand, for the subsequent software error checking, software upgrade caused trouble. As an early programmer, technical documentation takes up 30% of the time, while advanced programmers, system architects, and so on, require more time. General Software documentation requirements, this article does not say, you can review the pre-employment software documentation requirements and styles.

2. Extensive reading

Most programmers are short of reading, and perhaps not at work, but this is not an excuse to read in a programmer's self-improvement process. We can read a large number of books, periodicals and excellent source code, or even Weibo.

It is recommended to subscribe to the programmer's Journal " Happy Code Farm" which is compiled by the Code farming network, subscribe to the address >>

3, develop good coding norms and coding habits

As a number of well-known foreign software companies, such as Microsoft, IBM, Oracle, etc., will be the programmer to develop the code requirements, the code of the variable name to standardize, the key code snippet needs to comment, the annotation format is uniform, even nested line indentation length and the function of empty lines between the number has a clear requirement.

Chinese programmers, usually appear, the global variable abuse, annotation language expression is not in place, the variable name using pinyin, etc., although does not affect the development, but it has affected the subsequent code handover and share pay.

4, improve the understanding of software requirements

Myth: The novice programmer generally does not analyze the needs of the project and ask the people who need it, get the document, start to develop, in the B/s structure, more often the front desk needs and the back-end connection problems;

Therefore, in doing the demand, we should do, understand the requirements of the detailed requirements, and strive to put in place, to strengthen communication, understand the deep requirements of the content, especially the function points to achieve what requirements, how to use the system to feel comfortable. The grasp of the demand can not be understood from the perceptual point of view, must be more and work partners to collide, only to truly grasp the needs-experience. The real demand is just right, and what is needed is 2-3 years of time.

5. reusability and Modularization thought

Each programmer in the development of a functional module or function, should think more, not confined to the completion of the current task of the simple idea, think about, the design of the module can be separated from the system exists, whether the simplest way to modify in other systems or application environment directly referenced.

Through the two years of practice and observation, it is found that some of our team colleagues in the initial stage, often experienced code rewrite things, is not necessary, on the one hand, the idea needs to be re-established, on the other hand is a waste of time to improve the quality of code to do refactoring things.

6, exercise their own testing ability

Software development has always been a good tradition, software development process problems found earlier, the lower the cost of the solution. Test work is not actually troublesome, one is to do normal call test, see the basic function of the software can be realized, which is also common in many companies, but also the only test, but stressed that this is wrong! Second, the test of abnormal call, for example, under the B/s system commonly used pressure testing, destructive testing, frequency of abnormal request processing test, only a full range of test methods can improve the quality of software development.

7, the problem is the best learning opportunities

"Work is the process of discovering problems, analyzing problems, and ultimately solving problems," said the Japanese-run God Panasonic, who has always been open to those who solve problems at any time. "Visible, there are problems in the work process is normal, no problem is the real problem." In the event of problems, the courage to face the problem, solve the problem of the people, is the real backbone of the company.

How to improve the programmer's "performance"