The quality summary of the programmer should have gradually summarized

xiaoxiao2021-03-06  64

First, conscious articles

1. Teamwork and collaboration ---- Participate in open source software

2. Document habits - - from now

3. Standardized coding habits to ensure the readability of the code ----- Code standard

4. Not only do not pursue implementation, but also guarantee efficiency -----

5. Recise

Code stage and binary level

A module is not only multiplexed in multiple programs, but also in multiple functions of a program, minus overlapping;

6. Test as early as possible - the sooner found, the smaller the cost of solving

7. Learn again

Keep up with new technologies and improve efficiency;

Try to learn the underlying principle, improve the quality, such as design mode, network protocol, architecture, etc.

8. Summary

Summary each time a function is completed, finding insufficient, step by step;

9. There must be global awareness, architecture consciousness

Know the design of the modules, interface, and understand the architecture of the entire system throughout the system

Second, design articles

Demand analysis

2. Design method ----

3. Process Processing ---- Services, Data Flow, Data Dictionary

4. Re-use design and module decomposition ----

A function of a function, try to avoid repeating, such as Microsoft's Open File dialog box;

5. Overall project assessment

Resource configuration

Project schedule

Overall and module workload

Possible difficulties

These capabilities require the accumulation of experience; it is the capital of the old man, but it must be summarized, not the old people who will only repeat the labor;

Third, coding articles

转载请注明原文地址:https://www.9cbs.com/read-90005.html

New Post(0)