when I was ready to look at the book, I was not anxious to go through the content of the article. Because I usually read the habit of reading, so I first read the "Law of Construction" the book's catalogue, preface and even reader feedback. After a serious reading, I feel that the first version of the reader's feedback in the preface of the book is a highlight of my appreciation after reading the whole book.
The Book of construction makes me feel that the author of this book must be a weather-beaten, experienced programmer, and a literary scholar with a harsh pursuit of beauty. The book is full of literary and artistic breath. Skillfully combines the art and the boring programming perfectly, and combines the experience with the very popular text expression. The book is illustrated, and the pictures are very interesting and innovative, not a boring and boring ordinary teaching books. There are a lot of examples in the book, but also a lot of nicknames, and some news, examples of life through the Xin Zou teacher and our software engineering linked together. For example, the eighth chapter of the elderly people around China riding, the tenth chapter of the example of the hair cut pictures. Can see Xin Zou teacher is very attentively out of this book.
The content of the construction method is mainly to set up the scene, use a question and answer form for the software development testing and other areas of the common problems in the simplest words to answer, for some more difficult to understand the concept of strong professional nouns will be a story or scenario and small examples of our lives to explain, Let us understand its meaning in simple words or examples.
"The Law of Construction," the Book of Science and Thought analysis clear, simple and vivid and easy to understand, it is suitable for us these are not very professional people.
After reading the law of construction, I still have the following questions that are not very clear:
In the 4th chapter of the book, the two partners on the 75 page of the extreme programming (that is, pair programming), refers to a pair of programmers complementary development work, but in the book's 78 pages mentioned that the team's work can be exchanged for regular roles, but if one of the members of the code to write software, suddenly loaded with the role of the other person to After all, is not your own code, how much to browse the code needs to be familiar with the code process, then this process is not a waste of time?
In the 5th chapter of the book team and process, the introduction of a lot of team mode and development process patterns, faced with so many team models and development process, we face their own projects should be how to choose? What are the inevitable links between the choice of the team's model and the development process? In general, do you choose Team mode or development process first?
In the 15th chapter of the stability and release of the No. 306 page of the 15.1.2 Consultation Group, the book refers to the group of software team members of the team software bugs and other issues to meet the discussion to solve the problem, then the work of the group and Software testers conflict? Does this group of diagnostics discuss the issues that are left over after software testing?
The book of the Law of construction