Comments on: Rinse and Repeat with TDD http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/?utm_source=rss&utm_medium=rss&utm_campaign=rinse-and-repeat-with-tdd Dhananjay Nene's opinions on software programming, design, architecture and the internet Sun, 22 Jan 2012 06:53:20 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Kevin http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9212 Kevin Tue, 15 Dec 2009 16:28:47 +0000 http://blog.dhananjaynene.com/?p=921#comment-9212 I have read about TDD but never got a chance to implement it. The work environment plays a great role in TDD especially if you are maintaining someone else's code. If I get a chance to work on a fresh project, will surely want to try Rinse and Repeat TDD and see how it goes. I have read about TDD but never got a chance to implement it. The work environment plays a great role in TDD especially if you are maintaining someone else’s code. If I get a chance to work on a fresh project, will surely want to try Rinse and Repeat TDD and see how it goes.

]]> By: Dhananjay Nene http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9207 Dhananjay Nene Thu, 26 Nov 2009 03:29:03 +0000 http://blog.dhananjaynene.com/?p=921#comment-9207 <blockquote>The key is having the discipline to throw it away.</blockquote> Nodding my head in violent agreement. :)

The key is having the discipline to throw it away.

Nodding my head in violent agreement. :)

]]> By: Andrew Clay Shafer http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9206 Andrew Clay Shafer Thu, 26 Nov 2009 03:14:12 +0000 http://blog.dhananjaynene.com/?p=921#comment-9206 When you understand the problem, the spike is big enough. The key is having the discipline to throw it away. That applies to spikes of all sizes. When you understand the problem, the spike is big enough.

The key is having the discipline to throw it away.

That applies to spikes of all sizes.

]]> By: Dhananjay Nene http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9205 Dhananjay Nene Wed, 25 Nov 2009 17:20:06 +0000 http://blog.dhananjaynene.com/?p=921#comment-9205 Andrew, I have been using spikes for many years now, and am very pleased with the outcome. What is slightly different here is that the "rough code" I write is substantially larger in scope and size than typical spikes. Andrew,

I have been using spikes for many years now, and am very pleased with the outcome. What is slightly different here is that the “rough code” I write is substantially larger in scope and size than typical spikes.

]]> By: Dhananjay Nene http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9204 Dhananjay Nene Wed, 25 Nov 2009 17:15:18 +0000 http://blog.dhananjaynene.com/?p=921#comment-9204 Sasi, Starting with a fresh set of new files helps me ensure that I am able to write test cases with a substantially high level of code coverage. Its actually an interesting exercise to bring in small pieces of code one at a time to meet a small set of cases. Since the heavy lifting has been done earlier, the process actually works quite smoothly in an overridingly large proportion of cases. Sasi,

Starting with a fresh set of new files helps me ensure that I am able to write test cases with a substantially high level of code coverage. Its actually an interesting exercise to bring in small pieces of code one at a time to meet a small set of cases. Since the heavy lifting has been done earlier, the process actually works quite smoothly in an overridingly large proportion of cases.

]]> By: Andrew Clay Shafer http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9203 Andrew Clay Shafer Wed, 25 Nov 2009 17:12:41 +0000 http://blog.dhananjaynene.com/?p=921#comment-9203 I have quite often made the argument that trying to TDD solutions to problems you don't understand can produce some very convoluted code, particularly if your TDD cadence is Red-Green-Red-Green and not Red-Green-Refactor where 'Refactor' is the long beat. Luckily for us, the ancient wisdom of XP suggests a solution, which you have rediscovered. Write a spike solution, learn about the problem, then throw it away and TDD the production code. I have quite often made the argument that trying to TDD solutions to problems you don’t understand can produce some very convoluted code, particularly if your TDD cadence is Red-Green-Red-Green and not Red-Green-Refactor where ‘Refactor’ is the long beat.

Luckily for us, the ancient wisdom of XP suggests a solution, which you have rediscovered.

Write a spike solution, learn about the problem, then throw it away and TDD the production code.

]]> By: Sasi http://blog.dhananjaynene.com/2009/11/rinse-and-repeat-with-tdd/comment-page-1/#comment-9202 Sasi Wed, 25 Nov 2009 15:51:17 +0000 http://blog.dhananjaynene.com/?p=921#comment-9202 Actually my style of coding is pretty close to what you describe as Rinse and repeat TDD. And I am pretty satisfied with the overall quality (# bugs identified in QA being the metric). Starting with a fresh set of new files seems to be a bit much though :P Actually my style of coding is pretty close to what you describe as Rinse and repeat TDD. And I am pretty satisfied with the overall quality (# bugs identified in QA being the metric). Starting with a fresh set of new files seems to be a bit much though :P

]]>