First, my apologies for the length of time since my last post. I’ve been travelling and haven’t had good access to the internet. I’m at Agile 2006 now and will be posting updates shortly. However, on July 15th, I had the pleasure of speaking at the Tampa Code Camp at the University of South Florida in Tampa, Florida. All in all I got to present 4 sessions, and had a great time.
Perhaps most interesting from this code camp was the reaction to my Test-Driven Development and Ruby/Rails demos. In the TDD sessions, people were highly skeptical of the process we were following – especially writing failing tests with code that wouldn’t even compile! (“What about intellisense?!” was a common cry). However, as we worked through our example, it became clear what TDD was really about, and even some of the people who were shaking their heads the hardest seem to figure out what it was really about.
Another observation is how much vocabulary really plays into explaining concepts to observers. Writing a failing test which we’ll make green seems like quite an esoteric comment. But saying that we are going to write a test which shows that when we write the code we want to, we’ll know it works by them, seemed to come across much better. Don’t get hung up on vocabulary – it’ll bite you quite often if you do.
So, without further ado, here’s the presentations from my Ruby, Fitnesse and TDD talks. The fourth talk was to fill time when a presenter didn’t show up, and so there’s no formal presentation for it, since it was a combination of a code demo and chalk talk.
- Fitnesse
- Ruby
- TDD – Powerpoint and code
Thanks so much to the organizers, and especially to those who took a Saturday off to come out and talk about code. I couldn’t have asked for better audiences, or a better time.
Thanks for speaking at Tampa CodeCamp. Your presentation has sparked my interest in paired programming. Honestly, I could have spent the day listening to your experiences.
I was hoping to find the completed tests and classes for the bowling project. Strikes and spares are where the code starts to get challenging.
Do you have a completed version of the projects you can post?
Thanks for the kind words! The interesting thing about the exercise is how differently it can go based on the participants. I do, however, have a completed one I will get posted sometime next week (as I won’t be back to my home until Monday).
Glad you enjoyed it, and feel free to contact me anytime if you have any questions!
Thanks Corey. I look forward to the post. I was the bowler in the crowd and one of the guys you were following until we sat down.
I can see how the crowd can change the solution. Being a bowler, it is a natural domain for me to try out test-driven development. Thanks again.
Were you the “Ruby session that was very entertaining”?
http://blogs.msdn.com/sandyk/archive/2006/07/24/676811.aspx
Since I was the only Ruby session there, I must have been! That’s very cool – thanks for pointing it out.
And, in case anyone missed it, I have the full TDD Bowling code up on the web site, along with a walkthrough of me doing it Test-First.