Spotlight customer reviews:
|
Customer Rating: 
Summary: For the individual who wants to rise above the masses
Comment: In my role as CTO of a software firm, many developers ask me 'what can I do to move up to the architect/team lead role'.
Unfortunately it has as much to do with 'soft skills' in many cases and hard ones. Not good with people? It will be tough no matter what you read. This book however, is mandatory in my opinion if you are in this domain (and even in others as it is such an excellent example of what building a good reusable framework is all about, be it Java, COBOL or C#).
I would like to add something I believe others have missed. Although this book covers one dimension, you really need to cover the 'Domain Driven Design and Development' aspect for true optimal OO Framework reuse. Although this book is excellent, it should be supplemented with Eric Evan's work on Domain Driven Design in my strong opinion. Otherwise the full benefit would not be reached. This also adds complexity as it is assumed that an ORM framework is used, which today (early September 2007) means NHibernate. Perhaps some day Linq to Entities will work, but NHibernate is really a non-optional aspect now in reusable framework development (as are Mock frameworks, inversion of control and dependency injection, automated build server infrastructure, and much more that NEITHER book covers).
It's not for everyone, especially the lone wolf writing in his garage in a team of 1. If you have any code that would ever even have the chance of being reused (and even if you do not, you should write code such that it will), and if you are on a team of 2 or more, it is very, very hard not to implore you to read this.
Kind Regards,
Damon Carr
Customer Rating:
Summary: Great book for framework programmers.
Comment: Since I do a lot of framework programming for .NET, this is a great book. In fact, I consider some of the conventions listed in this book to be good practice even when not using .NET.
Customer Rating:
Summary: If you only ever buy one .NET book, make it this one
Comment: Simply invaluable.
This book encompasses everything a developer that has to design a piece of software needs in order to remain consistent with the rest of the .NET Framework and therefore make their API easily understandable and usable.
This book doesn't teach you how to use the .NET Framework. It doesn't teach you any language. It doesn't teach you tips and tricks.
What it does is teach you what you need to consider whenever you design anything in .NET. If I had it my way, I would make it so that wherever I worked - this would be required reading for anyone with enough experience to start designing software.
The only caveat is that there are a couple of guidelines there that are arguable, like the creation of new replacement types with numerical suffixes (see the TimeZone2 debate). However, 99% of everything written in the book is written in stone.
Customer Rating:
Summary: Best handbook for programmers EVER!
Comment: The authors were very modest in choosing their title. Yes, indeed, they focus on the scenario of writing reusable libraries, and write from the perspective of two of the designers of the .NET Framework. However, the utility of this book goes far beyond what the title implies.
If you actually write code,
If you actually design software,
on ANY platform,
and you dreamed of a book of which every page was packed with exceptionally useful, highly pertinent guidelines that will make your designs better and improve nearly every line of code that you write ... then this is that book.
Every recommendation is clearly presented, and the justifications are concisely, effectively and sufficiently argued, with the counterpoints and exceptions noted.
I would pay $5 per page for this book, and have found it to be, by far, the most outstandingly useful technical book I've read.
Two other reviewers have questioned the structure of the book. Do not be misled. The guidance is very well-organized, and super-imposing that organization is not the simple task that it might appear to have been. Also, the style of the book allows the argument for, and the counterpoints, to be presented concisely. If you not only want to know a good way of doing something, but find yourself either wanting to know why it is a good way, or, in your professional life, as a leader of teams, need to articulate why a particular practice is a good practice, then you will especially benefit from it.
In fact, when I was telling my wife how terrific this book is, I said that the style is totally unlike that of my own book, which is more rigid, stodgy and old-school academic--and I greatly envy Krysztof and Brad for having selected and perfected this ideal style for their material.
Another reviewer questioned whether this book is essential. Yes, it most certainly is. In the same way that I want my airline pilots to have pilot's licenses, I want my software development colleagues to have internalized this work.
Customer Rating:
Summary: invaluable to developers of class libraries, components, and frameworks--whether .NET or not.
Comment:
Excerpt from C# Online.NET Review (wiki.CSharp-Online.NET):
"The book is a codification of the set of guidelines worked out by the Microsoft .NET Framework development team to govern the project. It has been refined over six years. It's like the Constitution of .NET. But, the guidelines are so well crafted that the principles embodied in them apply equally well, not only, to all .NET languages, but also, to Java or any object-oriented language."
|
|
|
