Software Developer's work manual (Continuous collection Summary ~)

The following is transferred from http://blog.csdn.net/jinhuiyu/article/details/6534630

1. The programmer's career guidelines are: Honesty (Reporting your status, risks, and problems), keeping your word (the commitment to complete the task is done on time), respecting (respecting the colleague who gave you the code advice, and the wrong person).

2. It takes the same amount of time to write bugs and write code without bugs.

3. Bugs can grow, the longer survival time the more tenacious vitality.

4. If a stupid method can solve the problem, it is not a stupid method.

5. By dividing your work into an hourly target task, you will find that your work will be much easier.

6. Put the work you want to do one by one on the paper, finish a tick on the hook, you will like to tick the feeling.

7. Do not ask the customer how to do it, ask the customer to do so can not.

8. Let the customer to the various functions by priority, perhaps the customer will ask "anyway, all functions to be completed, why also priority." ", replied:" If a function does not finish to be beheaded, another function does not have to cut off the arm, I still would like to be beheaded first.

9. Try to make friends with customers.

10. Do not do what can not be done.

11. Performance evaluations may not necessarily be proportional to overtime hours.

12. Do not submit code that has not been compiled.

13. Do not submit code that has not been tested.

14. Do not submit code that is not review.

15. Do not tell testers how to test.