Share your TDD “horror” stories
I often run into teams who attempted to jump skull first into TDD and eventually threw their bones up in frustration when either schedules became scary or they ran into scenarios too frightening to test. Are there areas where test-driven development gives you the spooks?
We’re terribly excited to announce that on Tuesday, October 30th, we will be hosting a roundtable discussion on TDD at our lair in Reston, Virginia. Get into the spirit of Halloween by treating us with your horror stories on the trickiest problems when implementing TDD. We’ll be talking about what spells work and what spirits don’t, while mingling over a cauldron of fine wine (courtesy of Savoy-Lee), cheese, and other potions. We’ll also be raffling off a screamingly appropriate iPod shuffle.
When: Tuesday, October 30th from 5:30 PM to 7 PM
Where: Stelligent’s haunted headquarters (map)
Who: Ghosts, goblins, witches, and anyone who is screaming to use TDD or creepy enough to think about TDD
You need to RSVP, so please respond sooooon because tombstones are limited.

October 24th, 2007 at 1:27 pm
[…] If you are in the Washington, DC area, you will want to check out Stelligent's roundtable event on TDD on October 30th. I was fortunate enough to attend one of their roundtables in Boston on Agile, and it was a fun time. Andy Glover has an uncanny knack of putting together a really interesting group of people and seeding the conversation in a way that makes it flow. Well worth the price of admission (free
) […]
October 27th, 2007 at 5:46 am
[…] A tell-all night of TDD A wicked (i.e. terrifyingly hip) evening of TDD (that’s Test Driven Development, man) horror stories is taking place on Oct 30th in Reston, Va. I can only think of one other thing that could possibly be more fun (that’s disco dancing, man) so if you: […]
October 29th, 2007 at 8:25 am
[…] Don’t let one disappointing week stop you from subscribing, though– dctechevents.com. I think I’ll have some cool new stuff to show you next week. Tuesday: Share your TDD horror stories. Thursday: The New New Internet. Saturday: The Washington Digital Video November Meetup (group). Sunday: Washington DC Drupal Therapy.This intensive all-day workshop will arm novice and entry level Drupal users with a good schooling in Drupal basics, including installation, configuration, core functions, solid contributed modules, theme stunt driving and more. This workshops aims to provide quality Drupal isntruction in a price bracket that non-profits and small businesses can afford. […]
October 29th, 2007 at 8:28 am
[…] If you haven’t already registered for our un-boo-lievable TDD horror stories event, you better RSVP today before it’s too late! […]
October 31st, 2007 at 11:24 am
[…] The discussion then centers around the merits of unit testing and code coverage (much like the excellent discussions from Stelligent’s TDD Horror stories evening!)– for instance, one reader states: Striving for 100% unit test coverage is nice for libraries, but overkill for the avarage bussiness application that is written by most development teams. […]
October 31st, 2007 at 1:38 pm
[…] Lastly, if you’re local to the Washington, DC area, you’ll want to join me at Stelligent’s TDD Horror stories event on Oct 30th. […]
November 8th, 2007 at 5:08 pm
[…] In our first, “Share your TDD horror stories” event last Tuesday, October 30th, the turnout was quite “spooktacular”. It was the Stelligent staff who came dressed in costumes for the occasion, but it was the non-dressed in attendance that put on a good show in conversation around TDD scares. […]
December 10th, 2007 at 2:29 pm
[…] Does your organization actively practice test-driven development (TDD)? Chances are, the answer is no- at least based on the results of a survey distributed at Stelligent’s TDD roundtable, which found that the majority (84%) of the survey respondents aren’t practicing TDD, and 79% said they do not measure code coverage for development projects. […]
January 22nd, 2008 at 2:03 pm
[…] Test Driven Development, or TDD has quite a few different connotations; in fact, at our recent TDD horror stories event, the definition of TDD itself was split down the middle. Half of the attendees defined TDD as writing a test before writing any code and the other half defined it as writing tests for anything that could break (thus, not necessarily writing a test first). […]