last week the teacher gave us a class assignment: knot pairs to complete a arithmetic applet. As the class did not bring a notebook, so the class did not complete, but also observe the other students to complete the process. Knot to complete the project requirements are two students to work together to complete the project, after class back to the bedroom, and roommate to complete the work, the feeling is quite deep. Get this topic, first of all, we analyzed the topic, determine what language, what method to achieve, the topic is easy to ignore the question is what, need to use what method to optimize the whole program. This process is very important, because it is two students together to complete, so in the completion process will inevitably encounter different opinions, after all, thinking is impossible to unify, so in this case, two people have to listen to each other's views patiently, to avoid the occurrence of quarrels, disagreements. Co-programming, error rate will be reduced, but also more attention to the details of the problem, I was a weak programming ability, through pairing programming can also learn from the other side, two people to discuss together, it is not like the kind of holding the topic to eat under the hand. Two people programming together, the code of the normative is also very important, so the teacher also gave us a special explanation of the normative code, I think very beneficial. So, the power of two people is more powerful, pairing programming This method is also practical.
A bit of achievement |
Duration of study (h) |
Newly written lines of code |
Blog Volume (article) |
Learn the point of knowledge |
First week |
6h |
0 |
0 |
Preliminary understanding of software engineering |
Second week |
6h |
0 |
1 |
Understanding Software Engineering |
Third week |
10h |
0 |
1 |
Make questionnaires, understand requirements documents |
Week Four |
6h |
15 |
1 |
Learn to write requirements documents and pair programming. |
Thoughts on pairing programming