#KEYBOARD JUGGLER UPGRADE#This is good because it’s easy to upgrade an existing workstation. Each programmer has his or her own input device set, but the programmers share a monitor. Level 1: Good PairingĪt the next level, we add a second keyboard and a mouse. The only problem is that, of course, sharing information between users is difficult, so it may be hard if there is already work-in-progress when the pairing starts.Īt least this is better than the previous level, since both people can see the monitor equally well. Most operating systems make it easy to switch between users these days, so having a regular user and a pair user that can be switched into easily is nice. One way to help this problem is for the owner of the workstation to make a second user on the workstation, with its own desktop. The person who scooted over may feel like a fish out of water in an unfamiliar environment, leading to another situation where one person is doing all of the driving. Keyboard bindings, IDE color schemes, fonts, installed programs, and so on won’t be what a pair agreed to use, but what a single person prefers. This means that the environment will be configured for the workstation’s usual user. One of the problems of this set up is that it’s probably not a devoted pairing machine. If this is one person’s workstation that’s been re-appropriated as a pairing machine temporarily, the normal user of it may be more likely to hog the keyboard, so it’s important to be careful to avoid that. The two developers need to make sure they sit equidistant from the monitor so that neither person “owns” the machine and both people feel like they can grab the keyboard at any time. As long as you don’t make the mistake of filling your development area with corner desks, all that needs to happen here is have a second person scoot up to another person’s workstation. The great advantage to this setup is that it’s free. A rectangular desk with two people sitting at it, sharing a computer. The first level of actual pairing is simple. Put it in a cubicle so that it’s basically impossible for two people to fit and you’ve essentially ensured that nobody on your team will ever pair program. Corner desks are the office furniture from hell. #KEYBOARD JUGGLER DRIVER#The navigator will probably just zone out and think about something else while the driver codes away, confident that their pairing partner is helping ensure they don’t make mistakes. The monitor “belongs” to the person sitting closest to it, so the other person is really just watching. Just as importantly, the two programmers are not the same distance from the monitor. Trading places involves not merely sliding a keyboard over, but actually scooting rolling chairs out of the way, so it never happens. #KEYBOARD JUGGLER CODE#This set-up basically ensures that the person writing the code (the driver) and person thinking about the next steps (the navigator) never trade places. Nobody likes having someone read over their shoulder, let alone read code they are writing. It’s just coding with someone watching over your shoulder. That’s because this setup is not actually pairing. It seems like no coincidence that virtually everyone I’ve seen “pair program” this way dislikes pairing. Another person scoots their chair over and leans in, looking at the same monitor. An inside-corner desk, typically an individual’s workstation. The first level of pairing is something I see surprisingly often. I’ve had a lot of people ask me about how best to set up pair-programming environments at work, so I’m going to take you through a number of different ways to pair-program and discuss the advantages of each. I’ve tried pair programming with a number of different setups, each one better than the last. I’ve made no secret about the fact that I Love Pair-Programming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |