The book of the Law of construction

The whole book begins with the history of software engineering, from the beginning to the application, to the various changes that have been experienced. The next step is to become code to understand the strength of the group, to win the cooperation, to tell us about unit testing, regression testing, performance analysis tools. The middle part of the book mentions what it takes to be a software engineer: 1. Accumulate knowledge about software development and improve technical skills. 2. Accumulate knowledge and experience in problem areas. 3. Understanding of general software design ideas and software engineering. The second half of this "walk, after the development will be how, so no", how to do it, how to do wrong. For example, what is the macro perspective, what is best practice, what is called scrutinise. Like drawing a decision tree, to which branch to go, the result will be what, clear, clear, convincing people. The power of the whole is infinite. The final link introduces several models of teamwork, as well as several development processes in the team. Let me know from now on should focus on developing their own sense of teamwork.

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, a textbook that is in line with reality. It covers every aspect of the development of scientific and healthy Software engineering, introduces various methodologies, but not the methodology of high-up, programmatic, but the best practice of methodology, which is indeed available, and is used. This book introduces methodology at the same time, 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, "this way, 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.

In the introduction of methodology, the book does not put "people" into the "methodology" of the lower layer, but introduces a variety of roles, flesh and blood emotional people, can let students understand the work of the various roles and ideas, demands, avoid "to the program as the center" thinking, and understand people-centered thinking, after all, the program to solve, It's a human thing. This shift in thinking is crucial for programmers. This book covers the whole of modern software engineering, and every chapter and even every paragraph can be taken as a guide in practice.

In a word, this book, Brief Encounter, has a clearer idea of the way ahead.

　　　　

The book of the Law of construction