10 project habits that programmers should have

1, estimate the time to solve the problem. On the one hand to bear the responsibility, on the other hand to remember the last time to solve the problem, work as much as possible to use Google, StackOverflow and other tools, but encountered major problems, need timely feedback, we discuss together, must not be alone to explore, to believe the team.

2, pay attention to design mode. Most of the code is confusing because of the lack of good design patterns that lead to thinking. Of course, if the script is more effective in solving the problem, the script will be preferred.

3, do things to the wrong person. Problem, the first important thing is to solve the bug, rather than blaming the code of the colleague, this is really useful place. The team should help each other and develop together. In addition to the bad code, you have to put forward several solutions, rather than blame your code why this rotten.

4, do version control, do a good job of backup. Occasionally a colleague forces the code to be submitted, causing the other colleague's code to be lost, and then the first thing to do is to make a backup;

5, optimize the code, strengthen testing. The high quality of the code is that each person submits the code is high quality, so the business process, the code to be concise, testing complete consideration, then merge code, submit review.

6, familiar with the bottom, reuse mature code. Using code to provide efficient, familiar with the bottom can write better code. Example: If you need to sort and suppress the insertion of data, it is best to use hashset because of its data structure.

7, there is an error, it must be their own fault. Do not blame the tool, do not blame colleagues, their own patience to find the bug.

8, share. The team is composed of members of different backgrounds and technical conditions, need to share some concepts, tools, project experience or books, so that everyone in the same environment to work, rather than the use of each, causing problems, only to deal with their own, inefficient. Another week or two to open a technology sharing meeting is also necessary.

9, to have a global concept. For example, the different resolution of the terminal adaptation, code can be shared, cache management and so on.

10, design guidance rather than control development. Design the delivery of a draft, the strategy to complete it, tactical need to use their own professional skills to design the process, to be a savvy programmer.

10 project habits that programmers should have