45 habits of efficient programmers (practices of Agile Development)

2. The courage to admit that you do not know the answer is not the same as the courage to say unreasonable requirements.
4. When fixing errors, do not rush to understand the current logic and understand the current logic.CodeEncountered by other Group OwnersProgramDo not read the program, and ask for advice from other group colleagues.
6. Never be afraid to ask questions about sb. If you are stupid, you can express your questions as long as you know and think about it. Also, do not be impatient if you encounter some simple questions, and take them seriously.
8. You should be good at modifying bugs or looking at code with unreasonable code.Gradual and reasonableRebuild.
10. If possible, "lunch meetings" will be a good way to share knowledge and enhance team cohesion, however, it is difficult to implement it in an atmosphere where a company does not care about food or someone takes it to a restaurant.
12. When learning a technology, do not look at it from the old perspective, and do not use the C # syntax to write vbprograms.
14. Do not duplicate the wheel, but choose the right wheel. There are many open-source things on the internet, and choose the one that suits you.
16. When starting a project, it is best to have a customer representative resident project team as the only entry to the requirement. If the customer representative is not resident in the project team, it is necessary to discuss a suitable period to frequently present the Customer Code Demonstration System to quickly obtain feedback.
18. Consider the warning as an error.
20. DailyLiYes, it is standing, not an example.
22. If you try to rotate people in different release, do not create an atmosphere of who is responsible and who is responsible.
24. Note is required for SVN submission, and each submission is for a bug, that is, this submission is related.