by Robert C. Martin, Micah Martin
|
| List Price: | $64.99 |
| Amazon Price: | $51.99 & eligible for FREE Super Saver Shipping on orders over $25. |
| You Save: | $13.00 (20%) |
| Average Rating: |  |
| Lowest New Price: | $47.65 |
| Availablitiy: | Usually ships in 24 hours |
|
 |
|
No Editorial Reviews yet
Customers who bought this item also bought
Average Customer Review:
0 of 0 people found the following review helpful:
 Most C# developers fail on OO Design/patterns - fix it with this book, 2008-09-05
Other reviewers are predictable in when they say 'this is not C# or agile' what they are really saying is 'I do not want to learn OO design'.
Agile teams must have OO design mastery or they tend to iterate to release 1 with legacy code. After that it is a disaster to change or make long-lived.
If you actually believe that agile lets you neglect OO design expertise that myth is put to bed here.
Are you a .NET C# developer who (forget agile) doesn'r really understand 'favor composition over specialization/inheritance'? Then read this.
You can work in software with a lot of gaps, but the content here defines what is mandatory for even moderate levels of team based success, and this is not my opinion this is proven fact over 10 years of our industry evolving.
Do you agree in the following as a common value of `good' for software?
FROM: http://articles.techrepublic.com.com/5100-10878_11-1050347.html
Good design
Well-designed applications offer software components that are more robust, more maintainable, and more reusable. Such applications should be able to adapt changing business needs without affecting design. For example, a banking application should be able to support new types of accounts without a change in the existing design.
Three key points of good design are:
Maintainability, which is the ease with which a software system or component can be modified to adapt to changing environments, improve performance, correct faults, or other attributes. Well-designed applications require fewer resources for maintenance and changes.
Reusability, which is the degree to which a software module or components can be used in more than one computing program or software system. Reusability of software components helps ensure faster development of software applications.
Robustness, which is the stability of software applications in extreme situations (e.g., maximum load conditions, erroneous user inputs). Robust applications have less downtime and can reduce maintenance costs.
Bad design
Nobody plans to create ill-designed applications. It often happens because of a lack of experience or because the app was designed quickly to meet an extremely tight deadline. Poorly designed applications usually have these problems in common:
They're rigid. A design is rigid if it cannot be easily changed. For example, a single change to heavily interdependent, rigid software could begin a cascade of changes in dependent packages. When such a program grows in size, the designers or maintainers cannot predict the extent of that cascade of change, and the impact of the change cannot be estimated. This makes the cost of the change impossible to estimate.
They're fragile. Poorly created programs have a tendency to break in many places when a single change is made. Simple changes to one part of the application can lead to failures in other parts that appear to be completely unrelated. Fixing those problems leads to even more issues, and the maintenance process begins to resemble a dog chasing its tail. Such fragility greatly decreases the credibility of the design and maintenance organization, which leaves users and managers unable to predict the future quality of the product.
They're not reusable. A design is difficult to reuse when its desirable parts are highly dependent upon other details, which aren't desired. If the design is highly interdependent, other designers will also be daunted by the amount of work necessary to separate the desirable portion of the design from the parts that aren't reusable. In most such cases, the cost of the separation is deemed to be higher than the cost of redevelopment of the design.
Still with me? Ok..
.NET developers historically have lacked (as compared to other OFA (one framework only) developers) at the very, very least) acceptable OO Design skills. I mean even remotely `predictably' acceptable. Sure I worked with many teams who were exceptions but they were all from other (Java/Smalltalk) environments. Even C++ developers can slant to a master of C, deep internals, and Fragile Base Class disaster (grin). So Microsoft would have been nuts as they have always know this to put multiple-inheritance into C#. I digress... This is relevant to the book I swear....
Uncle Bob Martin created a masterpiece here that is still just as (more?) relevant. It is utterly transformative for anyone who wants to be even remotely productive on a team of best-practice types.
FYI this is the book used when I teach 'Core Object Oriented Design for the C# Developer' around the country.
NOTE: Do not let the word 'Agile' fool you. This is a book about best practices in software design and development. Agile just assumes you already know this material, yet most I work with do not.
He provides definitive coverage of the most critical reasons for failure if you skip then. For example, inheritance in OO is wrong for most cases used today in .NET.
Liskov substitution principle
Read this (covered in detail in this book):
Kind Regards,
Damon Wilder Carr
http://blog.domaindotnet.com
0 of 0 people found the following review helpful:
Bob has given another excellent book, 2008-07-29
I have read Bob's books/articles over the last few years. He has a way of explaining a solution that I have never experienced in any other books. This book is not an exception to that. I enjoyed reading everypart of this book. Must read for a C# developers.
0 of 0 people found the following review helpful:
Practical agile principles for developers, 2008-06-17
Agile practices and design patterns written in a clear, concise way. Granted there are a handful of mistakes throughout the book, and the occasional awkward reference to a pattern that won't be covered for another 5 chapters, but they're easy to spot.
The information is presented just right - a little background info, succinct descriptions, and simplified code examples. Outstanding.
0 of 0 people found the following review helpful:
Excellent coverage for the C# domain, 2008-02-13
Very readable, entertaining, useful. One of the few books that has been easy to follow and enjoyable to read. Very good general coverage.
0 of 0 people found the following review helpful:
Read It!, 2008-02-11
I have purchased and read alot of books on software design and development over the years and I cannot think of a single one of them that I would rate higher than this one.
Price is accurate as of the date/time indicated. Prices and product availability are subject to change. Any price displayed on the Amazon website at the time of purchase will govern the sale of this product.
|
Store Categories
|