On the book of the Law of construction

On the book of the Law of construction

Open the "Law of construction", the first to see that the other readers of the book's reading of the comments, read these comments have aroused my curiosity, this book really have they say so good? Software engineering left me the impression that the more boring, then a book on software engineering, even if the vivid image is always escaped boring not? But the book review is the opposite, which let me have a desire to explore the impulse in the virtually be hooked up.

Read, found that the book is really like other readers feedback, the book is a written flesh and blood, with a strong practicality and super fun, vivid image of people are easy to read the book.

The content of the book mainly to set the scene, the use of 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.

As mentioned in the 11th chapter of the Software design and implementation of the 11.5.2 daily build, at the beginning I saw this little headline, the head would like to be what things are built every day? And it needs to be built every day? Even reading the book citing the success of the software industry, "in our global survey, we found that 94% of successful companies are built every day or at least once a week, and the vast majority of the companies that do not succeed are built on a monthly or even less ..." feeling this is a little exaggerated, even too abstract, The importance of daily builds is not understood. But in this sentence is given a vivid dialogue, and the building of the example interspersed in the context of dialogue, which is the real example of life, so that we can be very objective, it is easy to connect it with the building building, it is necessary to build a building scaffolding, because all the workers have to transport the material on the ship, So it is necessary to build a scaffold that is particularly strong because it is about human life. The same reason, the daily construction is like scaffolding, need to stand every day, fall down on the trouble. Programmers who do not build are like the non-scaffolding, the dribbling of unfamiliar players ...

This book, in addition to the interpretation of the content of this scenario set aside a question and answer form, in each chapter has. As the 6th chapter of the Agile Process 115 page ~121 6.5 Agile Question and answer, (such as Q: What is Agile methodology?) A: The more famous is: Caressing brother (Fdd-feature driven Design), Skrom (SCRUM), Extreme Programming (XP). ）。 This way not only to the content of the changes to the summary and expansion, but also for our readers to solve the doubts, at the same time let the reader to a certain extent, the change of knowledge to do a review, deepen the impression of the content.

The law of construction is one of the most interesting books I've ever read about software engineering, and it's the only book I can read with relish. The Book of Science and Thought analysis of clear, simple and vivid and easy to understand, it is suitable for us beginners.

After reading the law of construction, I still have the following questions that are not very clear:

(1), in the 4th Chapter two people cooperation 75 pages mentioned in the limit programming (namely 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 on a regular basis, but if one of the members of the code to write software, suddenly loaded with characters, Another person to take his code down, after all, not their own code, how much to browse the code needs to be familiar with the process of code, then this process is not a waste of time?

(2), in the 5th chapter of the book team and process, introduced a lot of team mode and development process model, 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?

(3), in the 6th chapter of the agile process of agile questions and answers on the 117th page of the famous Agile methodology: Petting younger brother (Fdd-feature driven Design) and Skrom (SCRUM), what is the specific method? How should I understand that?

(4), in the Book of the 9th chapter of the project manager, has always been around the PM to expand, where PM is divided into Project manager and program Manager (Microsoft), then the other companies will set up Programs Manager, Or does a company set up project manager and program manager at the same time?

(5), in the 13th chapter of the user experience, the user experience mentioned in the SOFTWARE PRODUCT is not developed this first according to user needs and developed software Rapid Prototyping (book 6th Chapter 164)? Then according to the satisfaction of the user's experience to improve the software products?

(6), in the 15th chapter of the stability and release of the No. 307 page of the 15.1.2 Consultation Group, the book refers to the software team members of the team composed of teams of 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?

On the book of the Law of construction