6 would you prefer to write a large program by

This preview shows page 39 - 41 out of 41 pages.

We have textbook solutions for you!
The document you are viewing contains questions related to this textbook.
JavaScript: The Web Warrior Series
The document you are viewing contains questions related to this textbook.
Chapter 1 / Exercise 2
JavaScript: The Web Warrior Series
Vodnik
Expert Verified
6. Would you prefer to write a large program by yourself, or to work on a team in which each programmer produces one or more modules? Why?
7. Extreme programming is a system for rapidly developing software. One of its tenets is that all production code is written by two programmers sitting at one machine. Is this a good idea? Does working this way as a programmer appeal to you? Why or why not?
We have textbook solutions for you!
The document you are viewing contains questions related to this textbook.
JavaScript: The Web Warrior Series
The document you are viewing contains questions related to this textbook.
Chapter 1 / Exercise 2
JavaScript: The Web Warrior Series
Vodnik
Expert Verified
Programming Logic and Design, 8e Solutions 2-40 Student opinions will vary. Many will like the idea of working with another programmer; others will detest it. Pair programming is said to yield the following benefits: Increased discipline. Pairing partners are more likely to "do the right thing" and are less likely to take long breaks. Better code. Pairing partners are less likely to produce a bad design due to their immersion, and tend to come up with higher quality designs. Resilient flow. Pairing leads to a different kind of flow than programming alone, but it does lead to flow. Pairing flow happens more quickly: one programmer asks the other, " What were we working on? " Pairing flow is also more resilient to interruptions: one programmer deals with the interruption while the other keeps working. Multiple developers contributing to design. If pairs are rotated frequently, several people will be involved in developing a particular feature. This can help create better solutions, particularly when a pair gets stuck on a particularly tricky problem Improved morale. Pair programming can be more enjoyable for some engineers than programming alone. Collective code ownership. When everyone on a project is pair programming, and pairs rotate frequently, everybody gains a working knowledge of the entire codebase. Mentoring. Everyone, even junior programmers, possess knowledge that others don't. Pair programming is a painless way of spreading that knowledge. Team cohesion. People get to know each other more quickly when pair programming. Pair programming may encourage team gelling. Fewer interruptions. People are more reluctant to interrupt a pair than they are to interrupt someone working alone. One fewer workstation required. Since two people use one workstation, one fewer workstation is required, and therefore the extra workstation can be used for other purposes. Studies have shown that after training for the "people skills" involved, two programmers are more than twice as productive as one for a given task. Pair programming has the following disadvantages: Experienced developers may find it tedious to tutor a less experienced developer in a paired environment.

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture