Fixed spelling

Author: mattjmorrison

_posts/2013-11-27-pairtro.md

@@ -7,7 +7,7 @@ date:   2013-11-27
 
 I recently switched roles from a full time developer to a full time mentor. It was actually not much of a shift given my work environment. My team has 6 full time developers who [pair program][pairing] full time. Pair programming is a highly effective method of developing software and can be, at times, similar to mentoring. In an ideal pairing environment both developers are of similar ability. This ensures that both individuals can be equally engaged and equally contributing. When used as a mentoring tool it can be exhausting for each party. Pairing can be exhausting for the mentee because of a constant flood of new information and exhausting to the mentor for constantly providing the flood of information. This can, however, be a highly productive development and mentoring environment. 
 
-It is very important that each individual -- the mentor and mentee, knows their roles in this situation. While you both may be working on a feature, the primary goal of the mentee is to learn and the primary goal of the mentor is to teach. When either party loses site of their primary goal, things may fall apart. As with everything Agile, verbal (preferably face-to-face) communication is paramount. The mentor should give plenty of feedback to the mentee, and the mentee should be encouraged to ask questions and talk about the current feature, the tools, development methodology, etc. Remember, the primary goal in mentoring is to teach, not to write features.
+It is very important that each individual -- the mentor and mentee, knows their roles in this situation. While you both may be working on a feature, the primary goal of the mentee is to learn and the primary goal of the mentor is to teach. When either party loses sight of their primary goal, things may fall apart. As with everything Agile, verbal (preferably face-to-face) communication is paramount. The mentor should give plenty of feedback to the mentee, and the mentee should be encouraged to ask questions and talk about the current feature, the tools, development methodology, etc. Remember, the primary goal in mentoring is to teach, not to write features.
 
 If the mentor is too focused on completing the feature they may neglect their mentoring responsibilities which may cause the mentee may become lost, confused, or frustrated. The mentor may monopolize the keyboard and not allow the mentee to drive. The mentee may be intimidated and not feel comfortable asking questions with their lack of knowledge about the technology, the tools being used, or the task at hand. The mentor may become frustrated with the lack of their pair's participation or their lack of input into the solution.