The source is clear-I read the path to mountains

Introduction
====================

Probably because it is listed in the translator's list of blog posts, I often get messages about new books in the first place. I knew the news of this "mountain migration" before the publication of "Avenue to simplicity. At that time, I was also worried, because it was also a "Tao" book. I also talked about software engineering in the background of yugong's migration to the mountains ...... In his blog, Mr. Yan Xin said that the "car" hit him with a view of Venus. Why am I not like this? Haha ~ At that time, I thought: when "the path to mountains" is published, I must take a good look at whether it is a good book or not. I should adjust my comments first ....

I haven't thought about how to adjust it yet, and the book has been snatched by my colleagues before I saw the first page. Some of the tasks are often the same, so there is no preparation or preparation. However, the fact that my colleagues have snatched me away makes me know that, in any case, this must be a popular book.

　
　
I. Source of vsts: MSF
====================

I am afraid of writing a book in a confused way. I can't understand others either. I often remind myself of this because I write books. Today, when I read Mr. Yan Xin's "The path to mountains", the first article said the following sentence:

---------------
Ask which channel to clear such, for the source of live water.
---------------

The beginning of the book explains my long-standing questions: how to clearly write a book. This sentence is taken from Zhu Xi's "view of books", so it is said how the reader "read the book '". In the same sentence, the source is cleared ".

The title "mountain migration" is not a philosophical "Tao". Simply put, it is "a method ". Therefore, this book was originally about "mountain migration ". The author puts Software Engineering (specific implementation) in place as a mountain migration solution. In these thousands of difficulties, the author gives two "methods": MSF and vsts. The former is an idea, while the latter is a method tool.

Note 1: I have never directly discussed a method, a good idea, or a bad idea, because this discussion is always focused on a specific background or scope. So I am not here to say anything about MSF and vsts. Here we only talk about books.

To be honest, before reading Mr. Zou's book, I was troubled by the "Official tongue twisters" on msdn, just like the "Jelly" in the book. Basically speaking, apart from knowing that "MSF/MSA is Microsoft's engineering theory", I have not obtained any valuable information from those tongue twisters. This kind of knowledge has become "Vernacular MSF" in "The path to mountains ". In a word, it is the software method recommended by Microsoft.

Simply put: A method. Just like agile methods, the MSF method also has several "Basic Principles"-it seems that after agility, engineering theory first talks about "principles. In addition to these principles, the book mountain migration also describes their ing in vsts-some specific functions.

This is probably the content of the first eight chapters. The first four chapters are the recommended parts.

　
　
2. The path to mountain migration is pragmatic
====================
The second part is the content after Chapter 12. This book builds a virtual project and creates a real-world drama around a complete project process called "director. We can clearly see the performances, mentality, and even look of every engineering role in this project (because there are beautiful illustrations ).

We often read some books about engineering implementation, which are mostly about certain engineering methods, tools, or process theories or (Interface) operation guides. After reading this, the reader is not necessarily knowledgeable or useful. All of these must be placed in a specific engineering environment before readers can discover problems. When a problem is discovered, the readers either give up or give up with fear. This is probably the case when the project is unavailable. The "path to mountain migration" is about engineering scenarios and application methods in specific scenarios. Therefore, you will see a statement like this:
---------------
Classmate: Yes! We need five work item types: Full (Agile development model.
......
A Chao: When the agile mode becomes forced, Where can it be agile?
---------------

Or some practical methods to cope with the event:
---------------
......
Classmate: You are reasonable, but the teacher asked us to use a full set of agile models. What should we do?
A Chao: You can go back and tell the teacher that this is the latest "simplified development mode for migration to mountains", which fills in the gaps at home and abroad. ^) is easy to use.
---------------

This paragraph is very enjoyable. If you do not know what a specific project is, you must use the full set of XX methods, XX mode, and XX process, this is often useful.

　
　
3. How to read this book
====================

The content of this book can be divided into several parts:
1. vsts and MSF Basics
2. Basic Qualities of Team Roles
3. Engineering Practice details and Handling Methods
4. A Chao's story
5. Use vsts

Generally, you can use this book as a Quick Guide to vsts, so you can use it to learn vsts and MSF. After all, as advertised, this is "the first original product written by first-line Microsoft vsts developers ". Similarly, for an engineering team, this book may also be used as a general reader for team members. In addition, if your team's "personal technology and collaboration spirit and skills" still need to be enlightened (in my opinion, many people have this need), take a look at the second article in this book (9 ~ Chapter 11.

But if I read this book like this, it would be a storm of things. Because these are about three parts: 1, 2, and 5, they are just the details described in the book and are far from excellent.

I have read this book. After reading the first four chapters, I have understood the ideological basis and principles of the book. Next, I am probably reading a conversation between a Chao, Daniel, jelly, and other virtual roles. I call it the story of a Chao ". In my opinion, "the details and (specific) Handling Methods of engineering practice" are just an expression of a Chao's thoughts. Therefore, the combination of the three and four parts is the essence of the book. These are the essence of the project decision-making made by the author using the personal characters hidden in the conversation, a piece of text, and a sub-account identity.

These things that average readers pass quickly are actually more detailed, and I think more. Similarly, we hope that the readers can put down their eagerness to learn what they have learned and read the story of Alibaba Cloud.

In general, reading this book can lead to drinking water and thinking. The drinker knows what it uses. Only by thinking sources can we find the value of thinking and MSF in the author's vsts stories, or the practical thinking of the author in the case.

May the reader be the source of thinking. I believe that the author's book "The path to mountains" also has such deep intention. If this happens, the "Tao" does not have to be explained as a "method.