----- Original Message -----
From: "jt" <jt@ee.net>
To: <midrange-l@midrange.com>
Sent: Sunday, December 09, 2001 9:07 PM
Subject: RE: "One person per product"


> Jim,
>
> This is why I reject the statement that the paired-programmer
approach is
> "controversial".
>
> I can't imagine any "sometimers" and even a lot of today's
hot-shots haven't
> run into the following scenario.
>
> After hours of furious head-scratching and incantations, one
programmer asks
> others to help debug a program.  After a few minutes, one person
says "That
> line right THAR...  ICBW, but looks like you don't want that
asterix on
> column 7...!"
>
> Okay, maybe not that exact scenario, but something similar is
played out
> thousands of times a day.  The paired-programmer approach is
nothing more
> than the extension of this from the area of debugging to the
area of
> development.

That's like extending ballroom dancing to bungee jumping.


> OTOH, the paired-programmer approach WILL APPEAR controversial,
because a
> lot of folks are still looking for panaceas.  There are none.

Sure there are- 'structured programing' 'three tiered development'
'object oriented programming'

I do use bull pen methodology in design, but not execution. And
with design touch ups, when hitches develop.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.