Programmer's path to Agility: The 18 Ops

Three agile themes were made at the company: Agile roads for existing projects, scrum, and agile software testing.

However, some people say that these attempts are from a management perspective,ProgramHow can we be agile? Come back, think about it, and combine the books I have read to summarize the following 18 articles, so I will name it "the 18 th palm of the Dragon. Everyone should be right.

1. Positive attitude. Focus on your work, actively seek help when you have problems, and be willing to help others. Be brave enough to admit mistakes. If you have never made any mistakes, it means you may not work hard.

2. Understand the requirements in depth. Try to understand as much a requirement as possible and do not rush into coding.

3. Do not be an ordinary citizen. Do not read the codes that are obscure by yourself.CodeAlso, ask your colleagues to read their own code to ensure that the Code is easy to read and understand.

4. Dare to give comments. When you discover a problem, you dare to raise it. Nothing can pass the ticket. This will kill innovation, accommodate your own unacceptable ideas, and contribute your own good ideas.

5. Continuous Learning and willingness to share. If you haven't studied for a long time and find many things unfamiliar, But if you study every day and learn very little things every day, don't see the new technology "back from home. Share your knowledge, improve your team, and improve yourself.

6. Maintain a proper pace. Don't take a day off, take a day off, and get on and off each other.

7. Actively communicate with customers. If you are not sure about the requirements, you must ask the customer to give suggestions and make decisions. But do not ask many questions that are worthless and time-consuming.

8. Pay attention to design. Every system and every function needs to be designed. agility is not without design. However, the design should not be too detailed, including the system structure or class responsibilities. The form can be varied, and the whiteboard, sketch, and paste paper can be reflected in the Code.

9. Early Integration and frequent submission. Note that submission does not destroy the code base. Run the test locally before submission to obtain the latest code, run the local test, and then submit the code. Atomic commit. Once the function is unavailable, you can roll back immediately. This can expose the integration problem as soon as possible, greatly reducing the bug fixing cost.

10. Use unit test to guard the code. Automated User Acceptance testing. This allows rapid regression.

11. automated deployment. One-click deployment is implemented as early as possible, saving time and knowing the required software and hardware environment as early as possible.

12. submit the application as soon as possible and receive feedback from the customer as soon as possible.

13. Be sure to make a personal plan and measure your progress every day. In scrum, you can use a standing meeting. You must have your own backlog

14. openly accept user complaints, take them seriously, and find out the reasons for customer complaints

15. Code can be collectively owned. Anyone can change their own code or their own code.

16. The code can speak and use your code to communicate with colleagues. The code should clearly express what you want to do. Keep the code concise and easy to understand, at least the public method is simple and easy to understand. Reduce the code comments and use meaningful class names, method names, and parameter names for explanation.

17. Separate and solve the problem. When fixing the bug, isolate other places. Just like fixing an electric appliance, the circuit board will be removed and repaired. For example, use mock or other methods.

18. display the error information to the customer. For example, you can add an error number before the error message to help developers locate the error in the error log.