The Rhythm of Test-Driven Development

gistfile1.txt

Title: The Rhythm of Test-Driven Development
Level: All; unit testing experience helpful
Duration: 50 minutes including 10 for questions

Description:
Test-Driven Development (TDD) would seem to be all about the tests. But if you
focus on writing the tests, you miss most of the value. In my experience, TDD
can take 2-3 times longer in initial development time. The most-often-stated
value comes with the lack of debugging time needed with production deployment.

However, TDD's greatest value comes in the future. Software must remain agile,
open to change. The Rhythm of TDD, often called "red-green-refactor," provides
that value. This talk is an introduction to Test-Driven Development with a
focus on building that future value.

I include a reading list with explanations of each recommendation.


Additional Information:
1. Chain of Instruction: I was taught TDD personally by James Grenning, one of
   the original signers of The Agile Manifesto. James was taught personally by
   Kent Beck who published the technique.
2. Platform experience: I am a new PHP speaker. However, I used to teach Cray
   Supercomputer operating system internals (assembly and octal) as Senior
   Instructor for Cray Research Software Training.
3. Twitter: @ewbarnard

To whomever reviews this gist: My sincere thanks.

This talk is an introduction to Test-Driven Development with a focus on building that future value.

I think a statement like this should come much earlier in the abstract, to summarize the talk before expounding upon that summary.

I include a reading list with explanations of each recommendation.

Remove this, not necessary for the purposes of the abstract.