15:[[1719190,{"by":"devmonk","descendants":2,"id":1719190,"kids":[1721407,1719263],"score":2,"text":"The following are some pair programming anti-patterns\" (ok, maybe just bad behaviors) that I've noticed:

1. Prematurely trying to optimize code.

2. Long unrelated discussion. (Note: this one you just have to let go and accept, or you risk #3.)

3. Being anti-social.

4. Always not sharing the screen. (e.g. Pair partner brings a macbook and then basically proceeds to program as if they aren't sitting next to you.)

5. Not listening to your pair partner because you are too busy doing something else.

6. Not doing what you said you'd do/doing more than you said you'd do.

7. Just not communicating.

8. Not ping-pong'ing/both partners not staying active (which results in zombie state).

9. Listening to partner, but ignoring feedback, as if they are an annoying popup in your IDE.

10. Providing too much (esp. negative) feedback to partner.

Those are just a few. What pair programming anti-patterns have you experienced?","time":1285239531,"title":"Ask HN: Pair programming anti-patterns?","type":"story","url":""}],[1720291,{"by":"IgorPartola","descendants":1,"id":1720291,"kids":[1721355],"score":2,"text":"","time":1285260841,"title":"Paper processor. What is fetch , decode , and execute?","type":"story","url":"https://sites.google.com/site/kotukotuzimiti/"}],[1720854,{"by":"ivey","descendants":1,"id":1720854,"kids":[1721337],"score":3,"time":1285268607,"title":"Human-powered Ornithopter Becomes First Ever to Achieve Sustained Flight","type":"story","url":"http://www.engineering.utoronto.ca/About/Engineering_in_the_News/Human-powered_Ornithopter_Becomes_First_Ever_to_Achieve_Sustained_Flight.htm"}],[1720978,{"by":"saundby","descendants":1,"id":1720978,"kids":[1721329],"score":2,"text":"","time":1285270335,"title":"Is It a Planet, or Not? Planets Flora and Mnemosyne? Really?","type":"story","url":"http://astrobasics.blogspot.com/2010/09/is-it-planet-or-not.html"}]]

user:	vogon
created:	September 23, 2010
karma:	1