I don't draw that conclusion from what I wrote. You're still sitting
together, writing the code together. Is more than conversing. Its more
than a meeting on a proper algorithm.... Its actively working together as
a small team, line by line. Its checking and double checking as you go...
Its not right for everyone, or every case, but can be very productive. I
know I really liked it. The momentum you could gain was incredible, you
could get up to speed each day quicker and the kludge points where a lot
of people begin to become weary or bored seemed to pass much easier.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/30/2011 08:58 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: Agile Development, Anyone?
In that case Bryce "Pair Programming" is nothing more than a new buzzword
for what lots of people already do, which is to converse with others
regarding the design of an application. If that IS the case then this is
just one more of my pet peeves with today's "new" programming
methods/paradigms. It is something that's been around since the age of
the computer that younger folks think they came up with themselves and
slap a new sticker on it. (a rose by any other name...)
From: Bryce Martin <BMartin@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 08/30/2011 07:38 AM
Subject: Re: Agile Development, Anyone?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
You're missing the point of pair programming. Its about tackling a
problem with 2 heads, cutting the thinking time down, and getting a
product iteration out. We can make claims about super programmers not
benefitting and yada yada yada... but if a super programmer is working on
a sufficiently hard problem then pairing with another super programmer
would make that problem much easier to tackle. This works especially well
when needing to melt two areas of expertise. Its not about syntax and
style... that is what the language and style guides are for. Its about
solving a problem with as few bumps in the road as possible. Two sets of
eyes means automatic double checking of the code, auto code review as
someone else had said.
Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
08/29/2011 03:58 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
Subject
Re: Agile Development, Anyone?
On 8/29/2011 1:26 PM, rob@xxxxxxxxx wrote:
But have you tried it? The few times I've done it, it was an
interesting
experience that seemed really productive. As long as you can keep on
track.
I haven't done "Pair Programming", but I've sat and written code with
someone else, usually when trying to repair older existing code. I've
also done lots of team design sessions. From that, I have no desire to
find someone to sit with as we explain why we write code the way we do.
Joe
midrange.com
