Pragmatic Programmer modernly 5
Recently read "The Pragmatic Programmer" book Chapter VIII, I had a productive session.
Chapter VIII is pragmatic project, several key factors make the project success or failure of the main discussion. The main organization and management team, workflow automation, project testing, write some aspects of the document and to make investors happy know-how.
First, I understand the need to revise those easy little loophole, or once these vulnerabilities too small, it is more difficult to handle a big loophole. Then that everyone should pay attention to environmental changes, such as changes in demand and changes in other hardware and software environment. I
Also understand the development team to have exchange, or team collaboration bad, can not play the team's strength, such as inconsistent documents. I know the team have a division of labor, so that it can work more efficiently. I also learned the orthogonality project
Each activity must be orthogonal, or an activity error, all activities will be affected, should focus on function rather than job titles are organized. I also understand that if the use of some powerful tools to automate, which can reduce the workload. all
You can automate as much as possible are automated, such as the project to compile, code generation, regression testing. I understand that to achieve this automation, it is necessary to build automation, pay attention to the final build, we must learn to manage automation, such as web site builder,
Approval process and so on. I learned that we have to learn to be able to help us homemade tools. Come to talk about the test, and be regularly tested, early testing, automated testing, not gentle test your program, the purpose of testing is not to pass, but to find the hidden
Problem, so to test the limits of the program to find possible problems, pay attention to the use, performance testing and usability testing resources. I also learned some methods of testing, test data than, say, regression testing, GUI drilling system for testing
Test and thoroughly tested. I also learned when to test and to continue to add new tests to measure more bug. I also learned how to write a document, to add comments in the code, write executable documentation, technical documentation writers do, make sure your order
And learn to identify the presence of a language can always change your ways. I also learned to moderate exceed customer expectations, listen more to the views of users, to understand the characteristics make them happy. Finally, I learned regardless of the outcome of their work is good or bad, should be self
Responsible for own work.
Overall, I learned a lot reading Chapter Eight, I understood more about the methods to do the project ,, do this project I will mention more awake and helped me better understand a basic programmer Claim. In short, I
Full harvest.