Seventh Week assignment

Q: Bad habits in pairing programming-have you ever experienced how to remind your peers to improve?

* Informal people: two people working together at a close distance, but not paying attention to personal hygiene and mutual respect. Before starting to cooperate, eat a lot of garlic came.

* People who like to give orders: always say to the person on the keyboard: "Go to the last line, add an anti-brace, and then ...". Instead of focusing on the solution and what to do next, he pays too much attention to some programming details.

* Spell checker: Sit next to you and correct each error character you enter. Of course, he had no time to really navigate.

* A hidden person: just knock yourself out of the code without telling anyone what he's doing. The navigator had to figure out the code on his own. There is absolutely no communication between the navigator and the implementers about what method to use and which design to choose.

* People who jump a lot: they like to do a wide range of jumps in the code so the navigator doesn't know where to go.

1.在我实际的工作中，一般都是女生在一起，并没有过这些不拘小节的伙伴。个人的仪表是对对方的尊重，如果我的同伴真的这样，首先我会提出一起去外面咖啡厅工作或者讨论，这样一般就会适当得体一些，并且给他口香糖吃。2.首先要肯定对方的提醒，其次也向他提出，我们应该首先解决问题，等一下再一起纠正这些编程规范。3.好像是开车的时候被人不断提醒一样，有的时候这点确实让人心焦，尤其是很多的拼写错误都是一时手误而且编程工具会自动提醒，当遇到这样的伙伴时，我觉得应该引导他像别的方向注意，在编程前就提出一定的问题希望帮忙留意。让其把重点放在代码上。4.以前在另一个课程设计时做过项目经理，这点倒是经历过，当时还是大二，编程水平高的同学没有现在这么多，一个组里往往会有一个超过别人很多的人，他的思路和使用的新的技术往往让人一头雾水。结构和代码也不太理解。这个时候应该做出改变的不只是实施者，还有看代码的人，要直接提出疑问，让实施者回答，并且多进行讨论交流意见，并且希望在编程中注释。5.在看别人编程时，修改代码时，因为不熟悉别人的代码，修改时大幅度的跳跃和转换，让人不知道整个工程的现状。这个时候可以适当让实施者停下，和他讨论修改或者跳跃的原因，理清思路。

Seventh Week assignment