Pair programming lessons of summary
"Bao Jianfeng from sharpening out, plum blossom from the bitter cold."
Do a full one week, finally will pair programming project done, only you know how sad, how much sense of accomplishment that only you know. This is really their own hands, from the initial confused now ripe for their bow a bitter tears at the same time, can not help but have a trace of pride: I was very powerful, hard to do or can do out of.
Project ideas
My teammates and personal items are written in C ++, so we chose this pair programming software is QT.
We project is divided into two parts: Sign section entitled display section.
Login Register we did a four part interface: login screen, registration interface, password and change the password screen interface;
Title display section has three interfaces: select the type of interface, the interface, and answer results interface.
In the production, we first make the basic framework of the interface, the use of knowledge, and learning to use slot interface to connect, establish internal relations between class and class in this way. We then implement the functions of the various components to complete the code corresponding module, which of course, there have been many bug, we have been kept debug. Finally, when the feature points are achieved, we spent a day and a half to beautify the interface layout, while the test run, fully functional.
Personal reuse project
Although this knot has been associated with programming and individual projects, but not quite the same as at the time of implementation, in addition to the papers generated function were multiplexed, others are basically re-written. Because here the user name and password is not a fixed number, but to use a registered phone number, the user's own password is set, therefore, to log individual events here can not be directly used. Individual projects are not subject to calculate the answer, but the pair programming options and also to have the correct answer, so this part is to be re-written. The re-check that part, due to the requirements of individual projects of the same questions an account generated can not be repeated, it is necessary to re-check from the perspective of the file, but the pair programming only need to set the test paper questions do not repeat it here use vector arrays on it. Individual projects need to switch accounts, but the pair programming and not have this requirement. To sum up, my teammates feel the papers generated only that portion of code reuse, and the rest are to be re-written. Of course, the papers generated in this part of the code is the core of the project, due to personal projects completed, in this regard, we would save a lot of time, so our pair programming time basically in the visual interface.
Lessons learned
1, pair programming, I get a conclusion that 1 + 1> 2, I think, if not cooperation program, are having problems I will take more time to resolve, I will have to do something out many features are not available, many details not considered. The most important thing is, when thinking into a dead two people together to discuss ideas easier to open, out of the woods.
2, to develop good habits of a record. When we pair programming beginning, I encountered a lot of mistakes, but we are usually a encountered a solution, but in the end they found the problem solved in front of, behind and will not be solved. Here is the most obvious problem is the output, because we are not familiar with the language qt, is not likely to debug, the result of wrong time to put an intermediate variable output, but do not know how QString output variables. Initially found a solution, output once, to solve the problem at the time, but later, when needed, they forgot how to output, again Baidu, wasting a lot of time. Then from this time, we should realize that with a documented problem we encountered, together with solutions, this will learn more things. Attached below records from the problem after we started to record.
3, life-long learning. Although this project done, but I know that this project is very simple to achieve functionality, and time may be later tested and found the problem now is not found. In the final stage of perfect code, every time we feel was perfect, but a test, there are some small problems, then we will begin to modify. Fortunately, this project we are classified written, modify them or encounter problems there have a clue ideas, which once again demonstrates the importance of the maintenance of modular programming changes.
4, communication is very important. Throughout the project, due to problems of communication, originally I want to say the other side get less, so many times since the argument, and there were times when we finally found an argument to mean that we want to express is the same. Like this case we spent a lot of time, but also exercise us, behind us to exchange up to smoother than the beginning. At the same time, I'm different personal habits, my personal habits from hard to Jane, point by the face, but his teammates from simple habits into difficulty, by the point and the surface, this can not say who is right, mainly to communicate, exchange have no, learn from each other.
5, control their emotions and peace of mind to write code. Because of this large pair programming work, time is tight, the middle and mixed with a lot of other things, so we were a little temper, particularly when the issue is even more irritable, and sighed transfer negative energy, and ultimately can not solve the problem. Later we learn from other teams, cheer each other, encouraging each other, a much higher efficiency.
All in all, every experiment is a learning opportunity to progress, this pair programming, really let us benefit a lot.