Cloud Foundry: Design and Architecture
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Vikas Hazrati on Nov 12, 2011
Pair programming is an agile software development technique in which two programmers work together at one workstation. The benefits of pair programming are well known and the technique is widely practiced. However, what is the best way to sit while pairing?
A usual way to sit is side-by-side but it has its own set of drawbacks. As Josh Susser put it,
While it is a good setup in a lot of ways, it falls short ergonomically. First off, both people have to sit off to the side of the display, which can cause leaning, slouching, and twisting to get into a position to both see and type. And it's also hard to actually look at your partner without craning your neck around. Even though the desk is wide, keyboards and mice take up room, so there can be a lot of jostling and adjustment on the desktop, and chairs and such can collide as well.
An alternate way to pair program is by sitting face-to-face. The alternate setup looks like the sketch below where the shaded portions represent the pairs.

According to Josh,
It's a lot more comfortable, we both get a better view of the screen, and it's great being able to see each other so easily while we are working together. We are seated close enough that it's easy to hear each other without raising our voices at all. And after a day of working in this arrangement I feel a lot better and my neck doesn't feel out of whack.
Brian and Corey tried this model and found it to be quite effective. According to Brian, he ended up preferring this way of pairing than the conventional way.
I found myself preferring this style to pairing side-by-side in front of a screen. I even prefer it to sitting in front of two side-by-side screens with two keyboards. The work is more free-flowing and conversational. It’s easier to note the other person’s body language. It’s easier to stop coding, look up, and talk to each other. I found the switching between people more fluid, with fewer episodes where we were both going for the cursor at the same time.
Dave smith suggested that this arrangement is not new and he had seen something similar in 1980 where two computer scientists sat opposite to each other with two large box CRT's between them.
Tim Ottinger tried this arrangement and did not seem to be completely blown away. According to Tim,
We just tried it. It didn't stink, but it turns out that we feel less connected to each other that way, and have to point with mouse instead of hands. It works, but it is more like the remote pairing experience.
Does this arrangement have any downsides?
Josh suggested that it is a bit difficult to pick up the subtle cues like when the partner is ready to take control of the keyboard and small hand movements which are otherwise visible when sitting side-by-side. It also increases the cost since it requires more equipment and floor space.
Whether or not this arrangement would work in the long run, it is sure worth a try. As Davis W. Frank put it,
I can confirm that this setup is less awkward for high-fives when your tests go green.
Agile Maturity Model Applied to Building and Releasing Software
Improving Software Delivery Cycles: Pre-requisites and Inhibitors
How ALM Supports Business Processes
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
Derek Collison discusses the goals, the design premises and patterns employed in creating the architecture of Cloud Foundry, VMware’s open source PaaS, unveiling internal architectural details.
Andrew Watson talks about the work of the OMG, where CORBA is alive and well (hint: in your car), UML and UML Profiles vs. custom Modeling languages, DDS and other middleware, and much more.
Sohil Shah discusses creating iPhone and Android enterprise mobile applications based on cloud services using the open source platform OpenMobster.
Paul Sanford presents the transformations supported by data throughout its life cycle, and how that can be better done with Splunk, an engine for monitoring and analyzing machine-generated data.
A common “best practice” for unit tests is to only write a one assertion in each test. I intend to question this advice by showing that multiple assertions per test are both necessary and beneficial.
John Rauser presents the architectural and technological evolution of Amazon retail websites starting with 1994 and ending with adopting Amazon Web Services.
Michael Stal discusses system architecture quality, how to avoid architectural erosion, how to deal with refactoring, and design principles for architecture evolution.
Every developer has had to integrate with another system, API or component. Tis article provides strategies to handle the change and for he separating system boundaries.
No comments
Watch Thread Reply