Test-driven development: two scenarios

A litte write-up on how teams recruit for TDD.

Scenario 1

Them: So, what do you think about Test-Driven Development?

You: That’s the way I program. It makes the process more efficient and the end product more robust.

Them: We have a strong TDD culture here, so we’re glad to hear that. Looks like you’d be a good match for us in that regard.

Scenario 2

Them: So, what do you think about Test-Driven-Development?

You: That’s the way I program. It makes the process more efficient and the end product more robust.

Them: Oh, great. Our app is a ball of messy code that breaks when we look at it. It’s not tested because our previous developer told us that in Ruby, testing is built-in. Aren’t you glad you’ll be getting down&dirty with it?!

Moral of the story

Developers: when showing enthusiasm for TDD, be aware of the context.