Operation Manual of software developers

1. ProgramEmployees' career rules

• Be honest-report your status, risks, and problems truthfully
• Trustworthiness-the task promised to be completed must be completed on time
• Respect-respect for youCodeColleagues who make suggestions are not right

2. WrittenBug No code or write Bug The time consumed by the Code is the same.

3. BugIt will grow, and the longer the survival time, the more tenacious the vitality.

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

5. By dividing your work into hour-level target tasks, you will find that your work is much easier.

6. Put the work you want to do one by one on the paper. After you finish one, you will get a tick.

7. Do not ask the customer how to do this.

8. Ask the customer to sort each function by priority. Maybe the customer will ask, "Why do we have to prioritize all the functions ?", A: "If one function cannot finish killing the head, and the other function cannot finish cutting the arm, I am willing to first kill the head ".

9. Try to make friends with customers.

10. Do not do anything that can be done or not.

11. Performance evaluation is not necessarily proportional to overtime.

12. Do not submit uncompiled code.

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

14. Do not submitReview .

15. Do not tell the tester how to perform the test.