José Lema posts a good review of the Framework Design Guidelines.. He is the first reviewer to mention the high level philosophical guidance Krys and I give in the first section of the book.  In some ways I agree with Jose, this is the most valuable part as it really informs the rest of the book which contains the much more logistical do...don’t guidance on nuances of your framework.  It is possible to get your naming conventions 100% right, use every member the right way and still fail to have a great framework if you miss the underlying principles. 

 

From Jose’s review:

These are the best thirty-one pages of the book (IMHO). Here we read that a well-designed framework is simple, expensive to design, full of trade-offs, borrows from the past, designed to evolve, integrated and consistent. A key take-away from chapter two is the Principle of Scenario-Driven Design. Rather than beginning with the object model and then finding a way to get key scenarios to work, the authors recommend the reverse. Start by writing how the code should look for those scenarios, then fill in the details.

 

Thanks Jose... and keep the feedback coming!