Today I noticed that Amazon has the Framework Design Guidelines in stock (finally)… you can also post comments up there now. Especially for those of you that already have a copy of the book from the PDC, please do post a review and let us (and your fellow developers) hear what you think of the book….
In honor of this day I thought I’d kick off a series of blogs discussing bits of information from the Framework Design Guidelines. I am looking forward to having some conversation on each one, so let me hear what you think! BTW – a full sample chapter is available from Addison Wesley here
DO explicitly design for a broad range of developers with different programming
styles, requirements, skill levels, and using different programming
DO understand the broad range of developers using multilanguage
PAUL VICK There is no magic bullet when designing frameworks for
picking up a programming tool for the first time through to industry veterans
building large-scale commercial applications. The key to designing a
framework that appeals to
them to get the job done with the minimum amount of fuss and bother.
Designing a framework that uses the minimum number of concepts is a
good idea, not because VB programmers can’t handle concepts, but because
having to stop and think about concepts extraneous to the task at hand
interrupts workflow. The goal of a VB programmer usually is not to learn
some interesting or exciting new concept or to be impressed with the intellectual
purity and simplicity of your design, but to get the job done and move on