Hello there!

The Explore DDD conference is only a few weeks away! Preparations are nearly done, but there is something we need your help with.

We are looking for a handful of volunteers to enhance the experience of our attendees and speakers throughout the event, by activities like introducing speakers, drumming up excitement with your colleagues, and answering logistics questions. We volunteers may take on other tasks, like facilitating a continuous retrospective and live tweeting the event. In short, we need ten or so people to be the eyes and ears of the conference, as well as to help the people on site get the most out of Explore DDD.

Candidates need to be available both days of the conference. Preference will be given to people who local and have an interest in domain-driven design, especially people who otherwise would not be able to attend. This is a great opportunity for students or professionals with financial constraints to participate in this first ever DDD conference in North America. Volunteers will receive complimentary admission and possibly other benefits.

I plan to assemble the volunteer team this week. Please email me at neontapir+ddd@gmail.com to apply for the role or to ask a question. I will be holding an informational meeting a week before the event to talk about the role and to answer questions.

I have volunteered for several conferences in the past, and I can say from personal experience that I get a lot more out of the conference as a volunteer than as a regular attendee. I ask you to consider volunteering with us. Thank you for your time and interest!

Chuck Durfee
Volunteer Lead, Explore DDD

The value of automated testing is predicated on trust. It begins innocently with a test suite that reports incorrectly. Maybe the test suite reports a lot of false positives, or maybe the test suite does catch enough failures. In either case, people stop running the tests. They stop maintaining the tests, and eventually the tests no longer function and are discarded.

For tests to remain relevant, this pervasive question runs throughout software testing: how can I trust that a unit test is actually exercising the code in question? This post talks about how mutation testing can provide a definitive answer.