Mount migration can also have a proper path-read the path to mountain migration

Mr Yan Xin, Senior Development Manager of Microsoft, finished reading the famous "migration path". Before reading it, he thought that if he only looked at the directory, what kind of questions do I have or what do I want to know most? Today, after reading a book, you can select a few topics you are interested in and share them with you in Q &.

1. Q: What do you think?CodeReview and pairing programming?

A:Code Review: checks whether the code solves the problem correctly within the specification. It mainly aims to find out the logic andAlgorithmSuch as errors or weaknesses, so that the code can be improved and play a role in mutual learning and promotion. Code review also enables developers to better understand the development strategies and processes of the project. Pair programming is developed by the interchangeable drivers and pilots with equal and complementary roles, peer programming can be reviewed and exchanged at any time, while bringing more work confidence and supervision.

Code review and Pair programming are quite different: During code review, not everyone deals with that code even though everyone gives their opinions, the reviewer may not be interested in the Code. The starting point is negative. However, Pair programming does not have a line like "your code" or "his code, when dealing with a piece of code, two people can give better comments and suggestions. In addition, code review is generally performed only when the code can be submitted quickly. Pair programming can write and review the code at the same time. The cost of modifying the code is smaller than that of the former. However, Pair programming is relatively costly.

2. Q: How many stages does a team lead?

A:Summary of the "mountain migration" and network search, the rough conclusion is as follows:

1) forming stage:

Members are highly anxious about work and interpersonal relationships.

Emotional characteristics of members: Excited, hopeful, skeptical, anxious, and skeptical

Psychologically: extremely unstable

As a leader, you should clarify the team's direction, goals, and tasks, assign roles and their respective responsibilities, and break down tasks into short-term goals that are easy to operate. At this point, the leader should have a fast-cutting guiding style.

2) storming stage:

Members work and interpersonal relationships: violent and turbulent

Emotional characteristics of members: tension, frustration, dissatisfaction, opposition, and resistance

At this time, the leader should have an influence to actively cope with and solve various problems and contradictions; instruct the members to adjust their roles and responsibilities; Invite the team members to actively participate in solving and making decisions

3) norming stage:

Members work actively and diligently

Interpersonal Relationship: established, most of the contradictions have been resolved

Emotional characteristics of members: trust, cooperation, loyalty, friendship, and satisfaction

At this stage, leaders play the role of promoters and encouragement, coordinate conflicts and competitions among members, establish a smooth cooperation model, and actively delegate authority to members to manage and motivate themselves.

4) Creation stage:

Members work actively and diligently, and the efficiency of the team is surging.

Interpersonal Relationship: Harmony

Emotional characteristics of members: openness, frankness, dependency, and strong sense of collective honor

The main task of a leader is to establish a team performance and individual performance evaluation mechanism to maximize the enthusiasm of members. At the same time, we must be aware of the danger and prevent a good team from falling down due to pride and complacency.

3. Q: How do I deal with the shortcomings of the Project Plan found during project development?

In the agile development model, in the project planning stage, we must first clarify that good planning and design are the beginning of everything. What should we do when we find that the previous plan is not reasonable during the development process? I read the books and web pages. It seems that everyone is mature by default in the planning phase, and the implementation phase will follow the plan.

However, if a plan fails, does it mean that the project will face a great risk of failure? Does it mean that re-planning is the best option if time is too late? I personally think that if there is a major mistake in the plan, if the time is too late, I would rather declare the failure than wasting the time for the next step. If it is just a bit flawed, you can consider putting the changed part in the next iteration of the development process.

Here, let's look at it!

4. Q: The software has been released. Will Zhuge Liang's meeting be more involved?

A:My opinion on this issue is that if we succeed, we naturally need to raise a toast. If we fail, we need to come to a meeting later.

First of all, if you succeed, everyone will have a credit and a reward. If you have been working together for so long, there will naturally be a lot of ups and downs to share with all the members, we can also summarize some successful experiences, learn other people's flashes, and help them improve and improve in the future. In other words, success is the peak of a failed corpse. After the event, Zhuge Liang's meeting paved the way for success on the "Code body" page. The lessons learned have been corrected.

In other words, no matter what it is, whether it is success or failure or not, after so long struggle and hard work, so much effort, together, eat, drink, and laugh, it is not too much.

5. Q: After reading "The path to mountains", what are your thoughts or comments?

A:The following is the voice of a non-software specialist:

To be honest, when I just learned the course "advanced software engineering", I felt a lot of anxiety, code, and software development... That's a boring master. I was even more upset when I remembered that I had to read a textbook. Finally, I found that I was wrong.

From the perspective of software development, the book "The path to mountain migration" connects technology with practice through the plot of the story in the whole process of stone project development of virtual wangwu village software development company, the entire team process includes project conception, project plan, development process, testing, and version release. This book is very lively and interesting, and has many "jokes". It looks relaxed and pleasant, and it is not as boring as I think, instead, it is worth reading to explain the connotation of technology and the way of team management and operation in a humorous form that integrates with a multicultural environment. As an entry-level player, we recommend you read it. Believe me, you will not be disappointed.

 

Finally, you do not need to "Zizi, sun, and sun are infinite" to move mountains!

Dongliang he