The book of the Law of construction

This semester's software testing course added the "Law of Construction," the book, this semester using their spare time to learn the book, feel benefited.

For this book you can simply have two words to summarize: "Professional", "grounding gas".

The beginning of this book is to explain to me what is software and what is software engineering. Nearly three years of college, to tell the truth has not really been to know what is software, what is software engineering, said some ashamed.

First of all, this is a panoramic book that will give you a better understanding of the industry, allowing graduates to be less surprised and unexpected in the process of unfamiliar to the industry, which is a textbook that integrates reality. Secondly, this is a best practice book, covering every aspect of scientific and healthy software engineering, introducing various methodologies, but not high-up, programmatic methodology, but the best practice of methodology, is indeed available, to use. Third, the book makes people have feelings, students on the "ancient" waterfall textbooks or "imported" agile books, will inevitably lack of confidence: this thing can do? Is it suitable for modern? Is it suitable for China? And if to the major forums, communities, or ask "experienced", often will harvest more negative information, so that the students have feelings of disappointment, so that the lack of feelings of the students willingly. But it is obvious that our industry needs more feelings of talent, better professional ethics and literacy, if the students bow before graduation, the industry has any hope to say? Xin Zou Teacher's textbook will let students know "should be so" and "can be so", from this point of view, boundless beneficence. The book introduces methodology at the same time, actually will introduce the methodology does not apply to the scene, the methodology in the reality is how to run off, it is like talking chess, "so go, after the development will be how, so no", how to do it, how to do wrong-what is the macro perspective? What do you mean by best practices? What do you call scrutinise? It is like drawing a decision tree, to which branch to walk, the result will be what, clear, clear, convincing. Five, this book in the introduction of methodology, did not put "people" into the "methodology" of the lower level, but introduced a variety of roles, flesh and blood emotional people, can let students understand the work of the various roles and ideas, demands, to avoid "program-centric" thinking problems, and understand people-centred thinking, After all, the program to solve is a matter of people. This shift in thinking is crucial for programmers. Through this book I have a new view of teamwork, I previously thought that the model of the software team is a person to assign a module, own responsibility for their own, there is no pattern to say, but after learning the "law of construction", I learned that the original software team has a variety of models, and each model is applicable to different people and needs. This is really an eye-opener for me. I was impressed by the amateur theater model, secret team, star mode waiting. These are all related to our life, I did not think of the original software team mode from our life how close. I feel like I'm going to graduate and get lost in my job. I find it rewarding to be able to read such a book. This will have a very important impact on my future work.

The law of Construction, the book of the book