Framework Design Guidelines by Krzysztof Cwalina and Brad Abrams, 2006

Lots of interesting food for thought in this book.  It describes guidelines for structuring your code.  Should this be a structure or a class.  A method or a property?  A namespace?  Multiple classes?  How should I format the code?  Well structured and presented as a discussion of the pros and cons, rather than straight rules.  They made it more interesting by including commentary by some notable technorati.  A bunch of smart guys, in other words.


Post a Comment

Required fields are marked *

%d bloggers like this: