Rethought (ii): How to take care of the new people in the team

When we're talking about taking care, we're actually giving the new couple a decompression. When we say tolerance makes mistakes, we actually say you can make one or two mistakes. Decompression is more like creating a better learning experience, or a more enjoyable way to learn.

Learning and building Systems

School, learning is inclined to theoretical learning.

At work, learning tends to be applied to learning.

Two different ways have different differences, that is, a breadth, a depth.

When building a system, usually we need a system that is basically working, followed by the process of continuous development of the system. Our need for deep understanding has become more important than breadth.

Therefore, in a product-oriented development team, in the early days they needed more developers with breadth and speed as support, and in the later years needed to be supported by depth.

Two kinds of talents can play an important role in different periods.

Learning experience

In cognitive design, the following learning experience is referred to as "flow". And in the course of our study, we will have a similar learning process.

As early as I learned Emcas and Gnu/linux time, also gave up, although at that time I have read the Linux kernel. However, there is no egg for theoretical study prior to application.

Usually we have a learning experience similar to the one below, and for a book The following experience seems like a good thing:

1. At the very beginning of learning, we need a bit of theoretical foundation and what we need to learn.
2. Then we need to build a simple and usable system to gain confidence. If we are not in this step to imagine, so simple, then we may give up learning. Or wait until a certain period of maturity, such as when I began to learn "design patterns", then the height of the book is too high. Until one day, I learned a book called "Head First design mode", only to re-read the Gof book, found that in fact, it is not difficult to imagine.
3. Then after I have finished a feature, I may continue to learn a theory that will support my next plan.
4. After that, I think this step may not be so difficult, because there is already the basis of the previous. If we fail in one step, we may continue to look for some reliable solutions or theoretical support.
5. 。。。
6. Until one day, we came to the front of a bottleneck, the existing solutions have not satisfied our needs. We may not have a better solution to this problem. So, we may need to create a wheel, but at this point we don't know how to build the wheel.
7. So we started to learn to build wheels.
8. ....

Only when we maintain a learning process, we will not retreat in this step of the plan, we can not shrink back.

How to take care of the new team

In front, we have said enough nonsense to support our headlines.

In the previous article, "How to build the ideal development team," We talked about pairing programming. There are at least three modes in pairing programming:

1. Coach mode. In my existing experience, this model will help the new people more greatly. Generally speaking, we are going to break down the task and then lead the newcomer to complete the task step-by-step. You may have noticed that the flow of the heart that was mentioned above. In this process, it is easy to understand what this is all about.
2. Navigation mode. In one step, experienced people are more likely to act as observation modes. Sometimes, when a newcomer doesn't know which way to go, he knows the hint. When a newcomer makes a mistake, it's best to watch Ta make a mistake.
3. Pair mode. The ideal pair programming is in this mode. Achieving such a goal requires a good rapport between two people and the ability to be close to one another. In one step, if you can balance the steps of two people, then the confidence of the new person must be a great help.

The use of pair programming can not only improve the level of new people, the ability of the elderly is also a great output. That is, we need to pass it on before someone else enters the idea in our mind. For programmers this kind of people will certainly have a great improvement, if you are not good at expressing words.

Conclusion

So, what we call care is actually a better learning experience.

1. At the beginning of the church how to subdivide the task and lead him to learn
2. Give him guidance and let him finish his work by himself.

Very often, we are confined to the second step, so we can not better guide them to complete the work.

Reprint Reservation: rethought (ii): How to take care of the new team

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Rethought (ii): How to take care of the new people in the team