Jesse Ezell Blog

Alok Srivastava has an excellent post discussing agile development and areas that can put agile projects at risk. I'm currently doing clean up on an agile project gone south, and I wholeheartedly agree that the issues he points out should be warning signs if you are considering agile development. That's not to say that agile is bad by any means, just that you should think carefully before you make the jump, especially if your project will have the issues Alok mentions:

Jared Parsons thought it would be nice if we could have a ReadOnlyList object in our generic template instead of IEnumerable. I think that's an excellent idea, so a few minor modifications and we have an even better solution, not requiring the generic constraint TWrite : TRead:

Have you ever gone to a restraunt with a menu that was just too big? Every once and a while I wind up at a place with a huge menu and it takes forever to choose what kind of food I'm going to eat. That's not a problem when I go to a steak house. When I go to a steak house, I know exactly what I want. A rib-eye medium well with a side of mashed potatoes. Removing options always makes it easier to choose the right thing.

As we rollout Microsoft Online Services this becomes a crucial factor especially when you begin to delve in to the laws and regulations of each country and how they implement data privacy.

I'm working on a series of articles about building an ESB on your own.

If you are considering using "cloud services," you should read this:

http://www.blogmaverick.com/2008/03/09/my-rules-for-startups/

Finally had a chance to dig into the NServiceBus code. My thoughts are here if you care (I'm sure Udi will respond with his thoughts, so comment there instead of here if you think I'm off base):