Pair-Programming with a Wide Gap in Talent?
efp asks: "I'm a graduate student and have a programming assignment coming up. We're encouraged to work in pairs and I've agreed to work with a friend. However, while I'm far from l33t, I've several years more experience than my partner. Are there effective techniques for pair programming with a wide gap in talent? I want us both to get a lot out of the assignment, and I do not want to do all the work (which has been specifically identified and disallowed by the instructor anyway). Navigator/driver scenarios? Index-card design techniques?"
you said "my partner" instead of him or her. you're doomed if you want to fuck her.
i don't think anyone has mentioned that job reviews are a zero sum game now at a lot of companies. Not everyone can get a great job review on a team, and the managers are under pressure to curve their reviews. when you team program, this puts performance reviews and the secret pressure managers have to not grant a great review at odds with this utopia of team programming people imagine. All of these "team" ideas are great, but companies secretly have it set up to where if your team member succeeds it DOES mean there is less for you: less raise money, less of a chance to get a great review, because one has already been handed out.