 Who was in Ninda Rising's talk on estimation and deception? All right, so none of our lapping audiences. That's fine too, because none of this is going to be already familiar to you. I'm just two words about who I am. I'm a freelance consultant. I'm interested. I used to be a programmer, so I know a little bit about tech stuff. Nowadays, I'm into consulting, which means I'm also interested in the dark side consulting and management and all that. Who's a programmer? Who's not a programmer? Interesting. So let's talk after. I want to know what you're interested in in this topic. But for everyone else, I think we should be on the same wavelength of what design means. But I'm getting ahead of myself. So practices, that's the essential point of this talk. Now, shape of the S, that's a good transition into another S-shaped thing, money, value. What am I hoping that you're going to get from this talk? My intention is that you come away from this talk with a better sense of why in agile design is approached the way it is. Why, what is the relationship between things like per-programming and test-reven development? Is it coincidence that there are those two things in, say, extreme programming and refactoring? Did they happen to be thrown into a pot and stirred? Or is there a deeper relationship? That's the first thing I want to talk about. I would like you to come away from this session with renewed enthusiasm for doing some practices that you have maybe doing, but not quite as much as you should or you think you should. Who's doing test-reven development? So there's some margin, right. Who's writing unit tests? We didn't raise their hand before. That's a joke. I hope that you can also, for those of you who are already doing test-reven development, so the others will be convinced to try it because they have a better understanding of how.