Comments on: Paired Programming and Test Driven Development

By: Sagopa Kajmer

Sagopa Kajmer — Sun, 07 Mar 2010 17:23:18 +0000

Good post.Very good.

By: Divx indir

Divx indir — Fri, 26 Feb 2010 12:18:48 +0000

Thanks good article

By: huseyin

huseyin — Mon, 14 Dec 2009 07:18:17 +0000

Thanks for sharing very useful information.

By: payal

payal — Thu, 03 Dec 2009 09:37:58 +0000

Thanks for sharing very useful information.

By: Tie Racks

Tie Racks — Thu, 26 Nov 2009 14:45:54 +0000

Thanks for sharing the programming part in your blog i really found this details much important as i deal with it………
So thanks once again for information you had provided..:)

By: Boquete Panama Hotel

Boquete Panama Hotel — Wed, 25 Nov 2009 18:39:10 +0000

Great information. I am subscribing your blog

By: neelmoney dot com

neelmoney dot com — Tue, 24 Nov 2009 18:09:20 +0000

Sometimes working with complected team make me boring. hey No way to fill like CEO. I am the programmer and developer as own . this gives me flexibility and many paired to each way.

By: DIY car hire

DIY car hire — Thu, 19 Nov 2009 07:11:05 +0000

In thinking back over a couple of experiences in team coaching and organizational change, I’ve begun to realize that there is more to success than just spinning up one or two “hyperproductive” teams. One experience was at the first company where I learned agile methods in 2002, and the other was earlier this year, 2009. In both cases, we achieved astonishing success in creating one team or a small group of teams that performed far outside the norm for their respective organizations.

By: perfume spot

perfume spot — Thu, 19 Nov 2009 05:38:04 +0000

When you’re the observer, read the code that the driver is writing as he or she writes it. Your job is code review. You should pay total attention, aiming to let nothing get by you. Think about possible bugs, larger issues, and ways to simplify or improve the design. Bring up errors and code that you find unreadable right away. Wait until the current tiny goal is done to bring up larger issues and ideas for design improvement. Jot these later tasks down so the driver can stay focused on the present tiny task. For example, if you see that the current code fails to account for a null input, write down on a piece of paper, “Add unit test for null input.”

By: Computer Service Sydney

Computer Service Sydney — Wed, 11 Nov 2009 07:37:31 +0000

In my experience of leading teams I’ve always found designing at the keyboard to be more expensive than at the whiteboard. What is important is to know when to stop the whiteboard work and start coding. Experience will tell you when you are wasting time designing and it is time to try something out in code.