Our board has undergone a few makeovers as well over the past couple of years. In the beginning we tried to do what everyone else was doing. We had a big board with several columns. But our shop was small (at it’s peak, three developers and a PM) and the extra columns seemed wasteful. We didn’t really have a QA team, for instance, because we were the QA team. A “Testing” column seemed like a waste because we practice TDD as much as possible, so testing is part of the process of development. Same goes for acceptance tests, hands-on testing and customer approval. It’s all part of the process of developing software. Personally, I don’t look at the different elements - like architecture, design, testing or customer feedback - as separate phases. I see them as the one thing: developing software. They are all necessary elements to reach the final goal of a completed, working, and trusted software feature.

In the end, we finally settled on was the simplest thing that could possibly work: Backlog, In Development & Done.

Our Backlog is every story card in our possession. We don’t categorize; we just let the customer prioritize. In Development is everything we’re working on during this iteration. Since we - the developers - do it all, then In Development carries a comprehensive meaning. And when all the bases are covered, regardless of what order they were performed (although I hope unit tests were written before the code was) then, and only then, does it move to Done.

What I enjoy most about our board is that it is so simple to read. It’s easy to determine what’s left to do (Backlog), what’s being worked on (In Development) and what’s ready for the next publish at the end of the iteration (Done). And I don’t need to worry about testing or customer approval because those elements of the development process are implied.

Recently, Jeff made a post about DRM-Free Music. Like all his posts, it’s a great read. But that’s not what I wanted to write about.

What I wanted to mention was this nugget from Jeff that had me laughing:

I’m sure that the moment man discovered fire, there was some guy nearby saying, “Too smoky. Can burn you. Lame.”

I laughed because, regardless of context, this is so true. There are people in this world who can manage to see the negative in everything. And from now on, when I run into those people, I’m going to recall this phrase that has stuck in my head.

And I’m going to smile

Thanks Jeff.

That all changed today when a colleague - and friend - opted for greener pastures. He’s returning to the company where he started his career as an intern, a place he is particularly fond of, and I cannot blame him for taking a job that more closely fulfills his professional and personal desires. I wish him all the best.

Still, our small team of developers just shrunk by one, and we need to fill the gap.

In a larger city this would not be a problem. We’d just advertise the position and the resumes would pour in. But our location is our biggest hurdle when it comes to attracting talented developers. We simply can’t pull from as large a pool as a city like Austin, Texas can.

So where do I work? Nez Perce County, a small county government in north-central Idaho. As one might imagine, it is not exactly a mecca for software development talent. But that hasn’t stopped us from trying. People we talk to are always surprised to learn that our tiny little IT shop in Idaho is practicing Agile techniques. Yet that is exactly what we’re doing.

We subscribe to Agile practices, Extreme Programming in particular, and we drink from the TDD fountain. We use Continuous Integration, unit tests, acceptance tests, and frequent customer feedback along with short iterations to write quality, maintainable code and deliver business value to our customers (which, incidentally, includes us, since we are also taxpayers; we’re our own bosses in manner of speaking).

We work in an open environment and every developer has two monitors at their workstation. We work closely together as a team and have an on-site customer to help provide rapid feedback.

What We’re Looking For

We realize that we’re a bit handicapped by our geography. We’re not going to see a lot of great resumes. So it’s important for us to identify candidates that have the capacity to learn and possess a passion for software development. Ideally, candidates for our shop would have the following qualifications:

• Knowledge of Object Oriented design and principles
• Knowledge/Experience with C# .Net, or a similar object-oriented language (Java, C++)
• Database experience
• Willingness to learn

Bonus points for knowledge/experience with any of the following: Gang of Four design patterns, Unit Testing, IoC, CAB and/or SQL Server.

More information about the position, including benefits and pay, can be gathered by contacting my boss, Randy Buttenhoff, via the Nez Perce County IT web page.

Turns out that there’s a very simple pattern you can utilize to handle this situation. It’s called the Notification Pattern. Jeremy Miller, .Net guru, has a very good blog post on this pattern. He uses it to illustrate a standard way to handle validation on domain objects, but it’s a valuable pattern in other cases too, as I’ll show.

As Martin Fowler writes in his article, the Notification Pattern can be as simple as “a collection of strings which are error messages that the domain generates while it’s doing its work.” This is, in fact, how simple our implementation is where I work. A collection of strings, nothing more. You can use something else besides strings - a rich object with many properties and a public interface - if you like. But for this demonstration I’ll stick to strings.

The easiest way to implement this in CAB is with a Service class. All that is required is an event and a method to call to get notifications. The interface to the service basically looks like this:

public delegate void ApplicationClosingEventHandler(List<string> notifications);

public interface INotificationService
{
   event ApplicationClosingEventHandler ApplicationClosing;
   List<string> GetNotifications();
}

And the Service itself:

public class NotificationService : INotificationService
{
   public virtual event ApplicationClosingEventHandler ApplicationClosing;

   public virtual List<string> GetNotifications()
   {
      List<string> notifications = new List<string>();

      if (ApplicationClosing != null)
      {
         foreach (ApplicationClosingEventHandler handler in ApplicationClosing.GetInvocationList())
         {
            handler.Invoke(_unsavedChangesNotifications);
         }
      }
      return notifications ;
   }
}

WorkItems, Presenters and other classes that know about the dirty state of their models can take a dependency on this Service and subscribe to the ApplicationClosing event. When the event is fired, their handler adds a notification to the list, if it needs to.

public MyPresenter : Presenter<IMyView>
{
   private INotificationService _notificationService; 

   public MyPresenter([ServiceDependency] INotificationService notificationService)
   {
      _notificationService = notificationService;
      _notificationService.ApplicationClosing += new ApplicationClosingEventHandler(AppClosingHandler);
   }

   private void AppClosingHandler(List<string> notifications)
   {
      if(myModelIsDirty)
         notifications.Add("My object is dirty");
   }
}

The next step is to hook the whole thing into the Shell.Closing event. Back in the ShellApplication class, typically in the AfterShellCreated override, you can wire up to the Shell.Closing event:

public override AfterShellCreated()
{
   base.AfterShellCreated();

   Shell.Closing += new CancelEventHandler(Shell_Closing);
}

In your handler, you can query the INotificationService and get any notifications. If the notification list is empty, you can safely exit the application. Otherwise, pop a MessageBox and alert them.

private void Shell_Closing(object sender, CancelEventArgs ee)
{
   INotificationService notificationService = RootWorkItem.Services.Get<INotificationService>();

   List<string> notifications = notificationService.GetNotifications();

   if(notifications.Count > 0)
   {
      e.Cancel = true;
      // Alert the user
   }
}

That’s it. Simple, right? The nice thing about this pattern is that even with simple notifications, like strings, you can still give the user some very useful information on where unsaved changes exist. In our application, for instance, we let the user know which module and “use case” (very broad term here) contains the unsaved changes, so they can find those unsaved changes faster and make the save.

The Notification Pattern is one of the simplest, yet most useful, patterns that you’ll run into in any application, not just CAB. Now go forth and prevent your users from losing data when they close your app!

“So what do you guys think: Ancient Mayan temple off the beaten path?” - Jeff

Conventional wisdom says the beaten path exists for a reason: it’s safe. But conventional wisdom isn’t much of a match for a group of young travelers who wish to avoid “tourist traps” while on vacation. And so, with little reservation, best friends Amy (Jena Malone) and Stacy (Laura Ramsey) head off to an ancient Mayan temple at the urging of their boyfriends, Jeff (Jonathan Tucker) and Eric (Shawn Ashmore).

The group has been intrigued by a foreigner named Mathias whose brother, Henrich, has gone to the temple with his archaeologist girlfriend. Neither has returned, but Mathias quips that it’s probably because they’re having so much “fun”. At an old Mayan Temple. In the middle of nowhere.

Queue scary music here.

Amy gets cold feet when the group comes to an apparent dead end, only to find that the trail has been concealed with bushes. A couple of silent, young children show up several yards away in a creek bed to manufacture tension because apparently young children are scary. Amy’s intuition is to turn around and go back to the cushy confines of the hotel and pool. Why her boyfriend Jeff prefers visit dusty old ruins instead of jumping her bones at the hotel is a mystery.

No sooner does the group arrive at the foot of the ruins than some gruff looking “natives” arrive, complete with horses, guns, bows and arrows. They seem very threatening from the word “go.” A language barrier prevents either side from being able to explain themselves, and soon thereafter things turn bad. Pretty soon the tourists find themselves atop the ruins, unable to leave thanks to the folks with bows and guns.

To reveal what happens next would spoil the surprise of “The Ruins.” It is sufficient to say that it is probably what you did not see coming. In a way, “The Ruins” can thank recent horror films like “The Descent” and “28 Days Later” for priming its audience. Viewers will likely enter “The Ruins” thinking they have an idea of what to expect. They will be wrong.

Like “The Descent”, “The Ruins” doesn’t play any dirty tricks with its audience. It stays faithful to the rules it establishes early on. But unlike “The Descent”, the film only works because of a bit of manufactured drama, namely, the “natives”, who serve to keep the tourists trapped in their predicament. The film justifies this mechanism logically, but even so it still feels forced and mechanical, and detracts from the overall quality of the movie.

Still, “The Ruins” works. It achieves what it sets out to achieve and does so with a fairly creative horror device. It’s not as good as “The Descent” or “28 Days Later”, but it deserves a seat at the table.