Here is the PDF version of my talk, Test Driven Design for Ruby and Rails.
Search
About this Entry
This page contains a single entry by zenspider published on April 22, 2006 5:48 PM.
Silicon Valley Ruby Conference was the previous entry in this blog.
Where is our "magic-removal branch"? is the next entry in this blog.
Find recent content on the main index or look in the archives to find all content.
Categories
Monthly Archives
- April 2008 (2)
- March 2008 (9)
- February 2008 (5)
- January 2008 (15)
- December 2007 (14)
- November 2007 (5)
- October 2007 (4)
- September 2007 (6)
- August 2007 (17)
- July 2007 (13)
- June 2007 (8)
- May 2007 (20)
- April 2007 (15)
- March 2007 (18)
- February 2007 (9)
- January 2007 (6)
- December 2006 (7)
- November 2006 (6)
- October 2006 (11)
- September 2006 (17)
- August 2006 (10)
- July 2006 (5)
- June 2006 (2)
- May 2006 (6)
- April 2006 (15)
- March 2006 (10)
- February 2006 (3)
- January 2006 (5)
- December 2005 (5)
- November 2005 (4)
- October 2005 (5)
- September 2005 (2)
- August 2005 (1)
- July 2005 (2)
- June 2005 (4)
- May 2005 (5)
- April 2005 (4)
- March 2005 (6)
- February 2005 (12)
- January 2005 (7)
Pages
Looking forward to a version that works under Windows.
Thanks for your slides. Some of them seem to have had movies in the original presentation. Would it be possible to upload those, too?
Very nice, looking forward to diving in.
Very nice!
I noticed one thing right off the bat to take issue with. TDD does not change the the order of operations to put "Make it right" first, it just makes the cycles small. "Make it right" is the refactoring step, and that comes -after- "Make it work" which is to say, "make the test pass".
I do grant that TDD tends to produce code that is somewhat more "right" up front inasmuch as it tends to have a better calling interface, and it tends to do be loosely coupled, but one of the key benefits of TDD is to take away the stress of having to think too far ahead and design things perfectly up-front. Each item can be fractored once its test passes, so no messy code will left behind as a lasting smell.
Steve, I most respectfully disagree with your assessment. However, I'll give it some more time/thought/effort and blog my explanation when I can.