Just found this useful guide
Anyone new to [TDD] should begin with a partner who is more experienced, not only because it is safer but also because one can learn from the other’s experience.
Before starting the [TDD], it is important to have a general picture of the route and how it should be [TDD]‘d. If the [TDD] is long or has a crux, you should try to pick out in advance suitable spots to rest.
Three-point contact with the [code] is an important rule in [TDD] and should be followed where possible. […] You should always have eye contact with your next [refactoring] before you start your move. Scrabbling blindly about for a [refactoring] is a waste of energy. Once started, each move should be short, decisive and smoothly executed. Long moves will tire you out quickly and beginners need to spare strength for the final section of the [TDD].
From p. 17 “Rock Climbing Basics”, Johnston and Hallden, Stackpole Books, 1995
Very nice analogy.
I like the feeling that comparing coding to scaling a rock face gives me. It’s serious, skillful, exhausting, and thrilling.
Thanks.
[...] This post was mentioned on Twitter by SteveF , Philip Schwarz. Philip Schwarz said: RT @sf105: @jasongorman http://www.m3p.co.uk/blog/2009/03/06/tips-on-test-driven-development/ [...]