Happy Friday,

I used to speak at conferences around 6 times a year. That was before COVID. I always enjoyed speaking at conferences, but it certainly had its downsides. First, the cost of travelling to conferences added up quick. Second, the whole application process just drives me nuts. Despite that, I've enjoyed every event I've attended, met great people, and learned great stuff.

I really haven't spoken at another conference, though, since COVID. I just can't get back into the swing of it.

So when I get the chance to speak for the AgileLnL group, it's an easy yes, they're a great group organized by a good guy. A good guy I met at a conference!

This time I spoke about Test-Driven Development. I don't often do technical talks since there are better people than me for that, but TDD was on my mind after a recent engagement, and I thought I could do an interesting twist. What if I talked about TDD from the perspective of equipping a non-technical person on how to introduce TDD to a team.

I have a lot I can say on the subject of TDD, but what I will say is that TDD is the most impactful development process I'm aware of at this point. I've tried just about everything out there, and TDD stands apart as a technique. So it stinks that it is so easily bypassed and ignored by the development community. They won't even try it for the most part. Hence, if I could help non-technical folks with an approach that gets people to try it they can see its benefits too.

So that is what my talk was about. Introducing TDD even if you aren't technical. If you missed the talk, don't worry, you can watch it here.

I'd love to know what you think or what questions I didn't answer in that talk.

Sincerely,

Ryan