Timeline for How do you research while pair programming?
Current License: CC BY-SA 2.5
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2011 at 19:41 | comment | added | westcoastdiff | To clarify my answer. The non-typing member would generally only be doing research if code was not being written at that time. For example the typing member is building or researching too. @Johnsyweb I think it is important to recognize that pair programming (or anthing for that matter) is not an all or nothing proposition. | |
| Feb 12, 2011 at 14:53 | comment | added | traffichazard | I don't think I want to go this far - when code's being written, I want to be looking at it. I'm talking more about the situation where we both know what we have to do next, but we don't know how to do it - so we take a minute to look it up. | |
| Feb 12, 2011 at 7:53 | comment | added | jmort253 | If the person at the pair programming station is researching and not programming, then the catching up process simply involves a "Hey dude! Check out what I just found...". Just because both people are researching something independently doesn't mean they stop communicating. | |
| Feb 12, 2011 at 6:38 | comment | added | johnsyweb | If two people are working on two computers, that is not pair programming! | |
| Feb 12, 2011 at 6:02 | comment | added | Adam Lear♦ | Isn't the non-typer then distracted from what the pair's trying to accomplish? How does he or she catch up on what the other programmer accomplished while they weren't looking? | |
| Feb 12, 2011 at 6:01 | history | answered | westcoastdiff | CC BY-SA 2.5 |