----- Original Message ----- From: "jt" <firstname.lastname@example.org> To: <email@example.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.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.