Yes, the TDD debate really got me thinking about why I write tests. It used to be about saving me time. Now it seems to be about satisfying other people that I know what I'm doing.
But I am a fan of code-as-documentation, blindingly obvious business logic and data validations at the interface, and I was struck by how Uncle Bob's TDD example just disregards all of that. Hence the QDD piece (which is half serious, half joking; I've left it a puzzle for the reader to figure out which half is which).
