End-to-end programming experience

It has been more than a week since the start of pairing programming. Although the time is short, I still feel a little touched. Let me explain it in detail:

First understanding:

I am ashamed to say that I have never heard of the word "pair programming" before I took the soft work course at Yan Xin. For the first time, I saw the pair project in my assignment and required "pair programming ", I didn't think much at the time. I thought it was not just two people working on the same project. After the division of labor, the merger would be okay. it wasn't until when I really considered the first pair project that I had read a piece of the Rules to see the truth. I was surprised to see that I had to upload pair photos of pair programming. I was curious, bing, I learned that two people needed to complete the same project on the same machine, and then I realized that my understanding was so simple.

First conjecture:

After having a preliminary understanding of the concept of Pair programming, I have some doubts. Is it necessary to Pair programming? Can I really improve the overall work efficiency as I said on the Internet?

Will two different people write code together and "supervise" them? My coding level is so bad. What should I do if I am despised by pair? Does it really play a role in us? Can I really stick to it and finish my work under others' 'guide? Will this be just a form ...... With all these doubts, I started a pair trip with Yang. I thought, whatever the case, try a new method. Maybe it's really reliable, this allows us to complete our pair project within the specified time.

First cooperation:

With such an ideological preparation, we started our first discussion, discussed the rules, started some practical and specific planning, and briefly analyzed the difficulty and key points of the project, A simple division of labor. So what does the first discussion end? In fact, there is no strange feeling. It is similar to other cooperative programming, and I have not been able to realize the benefits brought by the pair. I think it may not be time to really understand it. The facts in the future also prove that, indeed, the true pair has not yet begun.

First reflection:

After a couple of days of pairing, we also discussed many times and the progress of the project. Then, when we discussed the implementation of some algorithms, we began to gradually disagree, although the difference was not big, but after all, I found that Yang was not able to concentrate on his thoughts, my brain is always thinking about whether or not my XX strategy can be improved. At the same time, I also vaguely feel that Yang is a little powerless when I come up with my own ideas. At this moment, I began to reflect: How can this happen? I should respect each other's views. Listening and analyzing carefully is the minimum respect for each other... But fortunately, we quickly realized this problem and achieved the same goal. We began to carefully analyze the methods of both parties and adopt appropriate methods based on reasonable and efficient principles. On the other hand, I also realized that Yang has done a good job in some details, such as managing some learning materials from the Internet and some new engineering projects, on the other hand, I did not do enough. The materials downloaded from the Internet are always not managed. In addition, I haven't shut down for several days, so that sometimes I can't find my own projects. I can only search for them through files, fortunately, Windows 7 has the file search function, or I still cannot find it. I realized this and began to manage my documents carefully.

For the first time, I realized the efficiency of pairing:

That was the key stage of project creation. for a whole day, we sat in front of the computer in the chair and talked about the general coding. Then we realized that pairing really could bring efficiency. Coding for a whole day is easy to get distracted. Fortunately, with pair, I always keep telling me the name of the member variable before I knock on the variable, when data is modified, it helps to check whether there are any missing ones. When variables and function definitions are used to get their names together, I feel a little confused and I changed my role, I also started to point to him. A person coding and a person review can indeed reduce unnecessary errors and vulnerabilities. After the algorithm is implemented, I will perform some simple tests together, after seeing the bug and analyzing it together, I can clearly feel that unlike my previous Personal programming, we can quickly find the initial bug point and propose a comparative modification method. Especially when you see the further implementation of the function, you are very happy. More importantly, you may share this feeling with you.

Let's write it here. I have a new experience. I will continue it ...............

Last left the truth: