Re: [OT] TDD + Pair Programming

2006-04-17 Thread Adrian Howard
Hi all, On 2 Apr 2006, at 01:04, Jeffrey Thalhammer wrote: I have never actually had an opportunity to practice this, but I've always felt that the most obvious way to combine test-driven development with pair programming was to have one person write test code while the other person writes appl

Re: [OT] TDD + Pair Programming

2006-04-03 Thread Steffen Schwigon
Luke Closs <[EMAIL PROTECTED]> writes: > On Sat, Apr 01, 2006 at 04:04:42PM -0800, Jeffrey Thalhammer wrote: > What makes pairing good is the increased attention to code as it > comes out. The pair discusses the implementation, which not only > finds lots of simple bugs very early, it also: > > -

Re: [OT] TDD + Pair Programming

2006-04-02 Thread Luke Closs
On Sat, Apr 01, 2006 at 04:04:42PM -0800, Jeffrey Thalhammer wrote: > I have never actually had an opportunity to practice > this, but I've always felt that the most obvious way > to combine test-driven development with pair > programming was to have one person write test code > while the other per

RE: [OT] TDD + Pair Programming

2006-04-02 Thread leif . eriksen
it is naturally reinforcing. If you struggle to get the approach to work, step back and try to see what is holding you back L -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Sunday, 2 April 2006 10:05 AM To: perl-qa@perl.org Subject: [OT] TDD + Pair Programming I have

Re: [OT] TDD + Pair Programming

2006-04-01 Thread Matisse Enzer
On Apr 1, 2006, at 4:04 PM, Jeffrey Thalhammer wrote: I have never actually had an opportunity to practice this, but I've always felt that the most obvious way to combine test-driven development with pair programming was to have one person write test code while the other person writes applicati

Re: [OT] TDD + Pair Programming

2006-04-01 Thread A. Pagaltzis
* Jeffrey Thalhammer <[EMAIL PROTECTED]> [2006-04-02 02:05]: > I have never actually had an opportunity to practice > this, but I've always felt that the most obvious way > to combine test-driven development with pair > programming was to have one person write test code > while the other person wri

[OT] TDD + Pair Programming

2006-04-01 Thread Jeffrey Thalhammer
I have never actually had an opportunity to practice this, but I've always felt that the most obvious way to combine test-driven development with pair programming was to have one person write test code while the other person writes application code. Presumably they might change roles periodically,