It seems in the last few weeks, there has been an especially hot debate around Ruby on Rails (RoR) and Grails. The debate on both sides has been respectful, and most importantly, a lot of good ideas are being exchanged.

In this blog so far, I haven’t made a habit of singling out other blog posts, although every week I read posts that deserve comment. But I feel compelled to point to Peter Williams’ “Mocking” post that I read this morning, because it shines a light on an area of software development that is relatively new and still somewhat nebulous, both for experienced test driven developers (TDD) and those who are not “test infected”: behavior driven development (BDD).

If you’ve scanned my blog in the past, you know that I am a big fan of Python and have been obsessed with Django recently, which to date is the most elegantly designed Web framework I have encountered. So far, other than using it on a very small project, I have mostly just been exploring Django and looking forward to using it on a more significant project that’s on my schedule for this summer. Unfortunately, it looks like I won’t be using it on that project after all, and the story behind it, which involves a good deal of office politics and my reasoning as I try to find a way through it, may be of interest to some.