| FlazX | Browse Computer Book | Community Board | Links | Blog | Login |
|
.NET Patterns: Architecture, Design, and Process
Google Search |
User review A well wrote book A very practical code book for everyone. The writer seems to hit all areas of being practical and yet pointing out patterns that can be used in a person's life everyday. I would definitely recommend this book to other people in the same field. I just happened to come across this not that long ago, while searching the internet. I am only hoping that the writer does another book and would be interested to see what he applies next. User review This book is not for WinForm developers The Patterns that the GoF are all applicable to WinForms, but this book assumes all web developing in its examples. I bought the book because I am a .NET WinForms developer so I if you are a web developer this book may help you, but it didn't do it for me. I found the original GoF book, `Head First Design Patterns`, even `Design Patterns for Dummies` better than this book. Also, it is unfortunate that .NET developers have to resort to these books and do not have a definitive Patterns book in any .NET language. The `Design Patterns in C#` is OK but that book has questions placed in there on nearly every page asking you to do something that isn't covered yet in the book which is bothersome. .NET developers would do well to stay away from this book even if you are a patterns lover. User review An Brilliant Contribution to our Field - Read 2-3 Times Amazon Buyer, The negative reviews puzzle me completely! I can only imagine the readers were expecting something different or didn't read the same book I did . Or do not build enterprise applications. I don't mean to say anything negative about my professional associates on Amazon, I just think (as a person addicted to reading ) that this book is absolutely, positively fantastic. There are so many nuggets of gold in this book. ANY serious .NET architect should have this publication on their book shelf. There are about 5 more core books, many by Addison Wesley, a company that in my mind is leading the pack in Software Engineering work. Just my 2 cents. If you would like my reading list please email as I am always happy to help those that are seeking a path. If I know your goals, I can probably certainly give you a set of books to get you to your goal. And again, I do disagree with the negative reviews but I do not mean any disrespect. Just friendly disagreement. Kind Regards, Damon Carr, CEO and Chief Technologist agilefactor www.agilefactor.com User review Practial Book on .NET Patterns I really don't understand the bad ratings of other reviewers. Either these reviewers didn't read the book or they are totally in love with theoretical issues on design patterns. This book shows hand on experiences - the authors shows REAL WORLD examples and illustrates how patterns are applied. I found the book very useful and it contains new interesting ideas on implementing PRACTICAL and USEFUL software applications with the .NET framework. User review Good ideas but,,. I have to disagree with most of the reviews here. I think the author has some good design pattern idea's. It seems like if a pattern book doesn't rehash the GOF's book for the 654654th time, its not a good pattern book. The author had some good ideas, and while most of the patterns are fairly focused to a specific problem and are not totally generic, it doesn't mean its not a good pattern idea. It's just a domain specific pattern. I think the author should have clearly specified that, but didn't and that was a mistake. He billed the book as a general user pattern book. So I game him 4 stars on that. But, in my job I'm very focused on code performance, so I knocked him back down two stars because these patterns are pretty much useless if you are designing anything that needs high performance capabilities, like web services. Most of the book is focused on patterns that he applies to web services, but he uses stuff like XML, DataSets and Reflection to create his abstraction layers. These three things are the 3 WORST performing features of .Net. If you are creating anything that needs to run `fast', you should stay away from all three of these. The pattern that killed me was his abstract packet pattern, which used DataSets or strongly typed DataSets to pass a list of parms between functions. He even hyped this pattern up based on performance reasons. I'd have to bet the guy never ran his code through a profiler to see what the performance implications of this pattern were. He made a lot of performance claims, but never showed the numbers to prove them, which is a dangerous thing because many developers will take what an author says as word, and not test the claim for themselves. So I think he had good ideas, but very poor choices with his implementation technology. Other books on .NET Patterns | |||||||||||
Google Talk : admin-at-flazx-dot-us