Pragmatic Programmer study notes 6

  The eighth chapter of this book is a pragmatic project.

  In the "pragmatic gang" section, first of all talk about the team as a whole, we should not tolerate broken windows. Followed by the team as an entity need clear communication with the outside world. It gives tips 60, "about the function, rather than the job title organized." Ensure consistent and accurate way is to make a good team doing everything automated.

  In the "ubiquitous Automation" section gives tips 61, "Do not use manual processes." When the project is compiled using the makefile There are several benefits. Construction of the project includes the following steps: 1, check out the source code from the repository 2, 3 build the project from scratch, create a distribution image 4, run the specified test. For most projects, to build this level is automatically run nightly.

  In the "test relentless" section, we give tips 62, "early testing, often test, automatic test." Tip 63, "going to pass all the tests, coding is not complete." The three main aspects of the project scope test is: What testing (unit testing, integration testing, validation and verification, resource depletion, and error recovery, performance testing, usability testing), how to test (regression testing, test data, drill GUI system test to test thoroughly tested), and when to test. It gives tips 64, "Testing your test by deliberate sabotage." Tip 65, "state test coverage, not code coverage." Tip 66, "a bug caught only once."

  In the "all written" section, I mentioned pragmatic programmers will document as an integral part of the development process to be accepted. It gives tips 67, "English as yet another programming language." Tip 68, "the document built on the inside, not tied to the outside."

  In the "great expectations" section gives tips 69, "moderate exceed customer expectations."

  In "Pride and Prejudice" section gives tips 70, "a signature on your work."

  Programmers introduced two world-class professional associations in the book appendix: ACM and IEEE. As well as some recommended journals, books, and other resources.

Guess you like

Origin www.cnblogs.com/songxinai/p/12122179.html