- Hardcover: 768 pages
- Publisher: Prentice Hall; 1 edition (July 30, 2006)
- Language: English
- ISBN-10: 0131857258
- ISBN-13: 978-0131857254
- Product Dimensions: 7 x 1.7 x 9.3 inches
- Shipping Weight: 2.8 pounds (View shipping rates and policies)
- Average Customer Review: 49 customer reviews
- Amazon Best Sellers Rank: #164,515 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Agile Principles, Patterns, and Practices in C# 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Frequently bought together
Customers who bought this item also bought
From the Back Cover
With the award-winning book "Agile Software Development: Principles, Patterns, and Practices, " Robert C. Martin helped bring Agile principles to tens of thousands of Java and C++ programmers. Now .NET programmers have a definitive guide to agile methods with this completely updated volume from Robert C. Martin and Micah Martin, "Agile Principles, Patterns, and Practices in C#."
This book presents a series of case studies illustrating the fundamentals of Agile development and Agile design, and moves quickly from UML models to real C# code. The introductory chapters lay out the basics of the agile movement, while the later chapters show proven techniques in action. The book includes many source code examples that are also available for download from the authors' Web site.
Readers will come away from this book understanding Agile principles, and the fourteen practices of Extreme Programming Spiking, splitting, velocity, and planning iterations and releases Test-driven development, test-first design, and acceptance testing Refactoring with unit testing Pair programming Agile design and design smells The five types of UML diagrams and how to use them effectively Object-oriented package design and design patterns How to put all of it together for a real-world project
Whether you are a C# programmer or a Visual Basic or Java programmer learning C#, a software development manager, or a business analyst, "Agile Principles, Patterns, and Practices in C#" is the first book you should read to understand agile software and how it applies to programming in the .NET Framework.
About the Author
Robert C. Martin has been a software professional since 1970 and an international software consultant since 1990. He is founder and president of Object Mentor, Inc., a team of experienced consultants who mentor their clients in the fields of C++, Java, OO, Patterns, UML, Agile Methodologies, and Extreme Programming.
Micah Martin works with Object Mentor as a developer, consultant, and mentor on topics ranging from object-oriented principles and patterns to agile software development practices. Micah is the cocreator and lead developer of the open source FitNesse project. He is also a published author and speaks regularly at conferences.
Top customer reviews
The book is worth a read because it contains some valuable information. Especially the chapters on the SOLID principles, the component packaging principles (analogous to the SOLID principles, but for components), and the chapter on component and class metrics that was very interesting. Those chapters are well written and I think demonstrate the principles well. Granted, you can probably find this information elsewhere. Probably why I rated the book a 3 instead of a 4.
In addition, the refactoring chapter was pretty good, too. And there were several chapters that covered the basic, most common design patterns that most programmers should know if they already don't.
The book was written in 2007, and so is dated. For example, there is no use of generics anywhere in the sample code. IIRC, generics came out just after this book was published. Therefore, some of the examples given don't translate quite as well to the features now available in C#. Secondly, you can tell the examples are translated from Java. The original Clean Code book written by Robert C Martin is in Java--as that is a language the he programs in often. His son, who helped write this book, does program in C# (and probably Java)--but you can tell the examples still have Java programming idioms in them. (Full disclosure, I'm not a huge Java fan--that's my personal preference.) More importantly, however, is that Java has it's own coding conventions adopted by those who program in it, e.g. getSomething, setSomething (since Java doesn't have syntactic sugar for getters/setters), no 'I' in interfaces, it's just a List, not an IList--unlike C#. But the authors routinely ignore C# coding conventions in their examples, such as using camel case for methods and preferring getXXXX/setXXXX over .NET properties, and not prefixing interfaces with 'I'. For the record, I agree with the authors that prefixing interfaces with 'I' should not be necessary, nonetheless, it's a .NET coding convention.
What I'd really like to see is the author update this book, including all the examples. Show us how you would write SOLID code using .NET generics; the role that lambdas play when writing SOLID code; and use .NET coding conventions throughout.
Other than that, as I said at the beginning, the book still has a lot of good information in it that makes it worthwhile to pick up and read.
The good points:
The book has aspects that will keep this book on the shelf, ready to crack open at a moment's notice: justification for denouncement of excessive documentation and diagramming, encouragement of realistic / sustainable work hours, explanations of design patterns in a (loosely) C# context, explanations of agile PPPs from an angle I had not previously considered, demonstrations on how to produce reliable software development estimates, emphasis on test-first design / development as the foundation on which this book is written, the list could go on (but not much further).
The stale points:
To be fair, any language specific examples will become stale pretty quickly, as technology is always advancing at breakneck speeds. The Author(s) do state early on that they're not telling you "how to do C#!"; rather, they're extending a lofty olive branch to the .NET developer community (thanks....?) and wanting to discuss more language agnostic topics (refer to the good points listed above). A lot of reviewers point out that C# is really just a namesake in this book. Therefore, let's just go ahead and say it: the C# is really stale; there are such amazing things C# can do now that have made the language much more expressive, maintainable, dynamic, and capable. Funnily enough, some of these advancements were called for in Jack Reeves' article included in Appendix B of this book when he was referring to C++'s success at its onset.
In a nutshell:
This book is worth having around. I will refer back to this book often for inspiration on various design patterns. However, I would like a more modern C# publication on implementing these patterns in a way that actually leverages the language and avoids (now) known anti-patterns. It would be grand if someone took the content of this book to the next level with more modern insight.
After having finished Agile C#, I experienced enlightenment in some ways, but at the same time, I need a C# palate cleanser.
One of the things I like about this is that it not only discusses Agile in C#, but it also has real, honest to goodness code examples. It also has more real-world examples of SOLID and non-SOLID code, with explanations of how to fix the non-SOLID code.
If I were to note one critical thing, I would like to see how SOLID ties in with Design Patterns.
All in all, if you're a programmer at any level, I would seriously recommend adding this to your library. Not necessarily for the version of C# (since that changes), but for the concepts therein.
I feel the take away from the chapters I read is , "Code today as if you're delivering tomorrow , design as if you're have a 5 year project" and you will get it done right.