3 ms·
Pair programming never worked (overall) for my partner and I. Generally, I found both participants have to be extremely focused, have roughly the same skill le
by cianestro 16y ago
Pair programming never worked (overall) for my partner and I. Generally, I found both participants have to be extremely focused, have roughly the same skill level, and the code should be worked out on paper before "iterating." Otherwise, we ended up arguing over trivialities or bird walks over to youtube in the moments where we both were stumped (more my partner--I'm not a big fan). Long story short, we use pair cowboy programming now with more success. I guess it's all dependent on the cohesion between partners' attitudes towards work; if partners' ethics are different use logical cohesion on a project else use functional cohesion (which is definitely preferred but not always an option). Hope that makes sense, just my limited take on the topic. Does anyone have any success stories with pair programming--I could use the tips!
- weilawei 16y agoI definitely recommend keeping sketchpads, graph paper, and a chalk/whiteboard around. It gives us a new mode of thinking in addition to plain old code.
- cianestro 16y agoWe have two 2x8 ft dry-erase boards actually. They have helped immensely during past meets. Surprisingly, Google Wave has helped us organize our collaborative coding a lot; Wave even has a brainstorm app (digital sketchpad) built into the client now.