begin quoting James G. Sack (jim) as of Sun, Jun 04, 2006 at 11:22:10AM -0700: [snip] > It's remarkable: once you become addicted to test driven development, > your code structure seems to change (improve!) just by thinking in > advance "how will I write a test for this feature/behavior".
I think the biggest advantage to thinking like that is when the time comes to write (or review) requirements. If a requirement isn't testable, what good is it? Getting good requirements is perhaps one of the more important skills to have when you're writing code for someone else. -- _ |\_ \| -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
