Agile Principles, Patterns, and Practices in C# / Edition 1

Agile Principles, Patterns, and Practices in C# / Edition 1

by Robert C. Martin, Micah Martin
4.7 4
ISBN-10:
0131857258
ISBN-13:
9780131857254
Pub. Date:
08/03/2006
Publisher:
Prentice Hall
Select a Purchase Option (1ST)
  • purchase options
    $63.30 $79.99 Save 21% Current price is $63.3, Original price is $79.99. You Save 21%.
  • purchase options

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

Agile Principles, Patterns, and Practices in C# 4.8 out of 5 based on 0 ratings. 4 reviews.
PaulGBrown More than 1 year ago
One of the few tech books I have read from cover-to-cover. The book explains Agile principles from a reality perspective. I really enjoyed reading someone who understood that getting the code done (and done well) is the most important task versus producing mounds of paperwork.
Guest More than 1 year ago
In one sense, the book covers no new ground. The Agile principles and patterns discussed here have been well explained for two other languages, Java and C++, especially by Robert Martin in an earlier book. What is offered here is a recasting in terms of C#. Which however has far fewer practitioners than the other languages. Some sections of the book are mostly independent of any language. Take the chapter on state diagrams for documenting finite state machines as one example. Or the other chapters on object diagrams, use cases, sequence diagrams and class diagrams. Some of these do have example code in C#. But inherently, they tend to stand above any language. Some principles are quite useful, albeit perhaps to an advanced programmer. A good example is the chapter on Interface Segregation Principle. Basically, it's about how an interface can grow, if there are several child classes that implement it. The problem is when some classes need routines added to the interface, that other classes do not. So we get a fat interface. This creates a cross-coupling that is unneeded, and a potential source of errors. Something that you should try to minimise, for long term robustness and ease of code maintenance.
Anonymous More than 1 year ago
Anonymous More than 1 year ago