Read the path to migration-vsts Software Development Guide

It took about a week to read the book "The path to mountain migration", and I felt that I had gained some knowledge. I used to simply compile a small program (even now ), however, after reading this book, I have changed my understanding of the concept of software development from a blur to a general concept. After all, reading such a complete book in one week is not a simple task. I just learned some things and encountered many problems during the reading process, some basic problems have been solved in later learning, and some are still bothering me.

(1) I learned a term in the book called work item, but I didn't mention a work item called issue in vs. What is the situation?

After understanding, I found that all vs involved in this book is vs2005. Due to the old version, there is no issue for this work item, while the current higher version of VS has issue. I have not used this work item in many practices, but it is quite convenient to use this work item according to my information, predict risks to cope with emergencies in Agile development.

(2) With regard to agile development, preliminary design is very important and may be easy to write at the beginning, but it is often found that simple methods are no longer available when Code increases in the future, inconsistency may occur. It may be complicated to rewrite later. Of course, the solution to this problem is undoubtedly to be fully considered before the start, but this seemingly simple method is almost no one can do it by, and it is difficult to grasp.

(3) Pair programming is an innovative programming method. Two people work together to complete an independent task. This method has both advantages and disadvantages.

There are many benefits, such

1) paired programming gives us more confidence on the premise of having a partner, and someone works with us. It is also more dynamic. It cannot be left behind by a companion, nor can it be left behind by a companion.

2) because two people work together, their thinking is more diversified and there are many methods. You can select the best one among the many options to improve the quality of programming.

3) Pair programming can communicate more effectively, learn from each other and pass on experiences.

Every coin has two sides. What are the drawbacks of having so many benefits to programming?

All programmers I Want To Know know that this programming method requires both parties to conduct in-depth communication and communicate well to ensure the quality of the Code. However, if both parties are not suitable for each other, the problem is big. I have never communicated with each other, or the habits of two people have become very different. I can't do what I do myself, and I can't find a proper way to cooperate, really Worried.

However, this problem is also well solved, so we should learn to combine the thinking and capabilities of both sides to solve the problem together.

(4) As long as this book has taken a glance, it knows that the whole book is based on a story, and it is fresh when it comes to contact, when I read the story, I thought it was a bit difficult to tell a story. It was very far-fetched and associated with knowledge. However, when I read the story, I became suddenly enlightened. I would like to review the whole book. If I didn't have this story, most of the things may not be understood or remembered. In short, this method is quite attractive and can make people better learn. But can this method be accepted by most people? I think we can do some research and solicit suggestions from everyone. We can continue to develop the good areas and modify the areas that need improvement. Maybe the results will be better.

(5) I did not find the answer to the last question. I have been thinking for a long time. Why can't Dev add tasks by itself in TFs? What are the restrictions?

Read the path to migration-vsts Software Development Guide