Agile Principles, Patterns, and Practices in C# (Englisch) Taschenbuch – 2006
Kunden, die diesen Artikel angesehen haben, haben auch angesehen
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Möchten Sie die Produktinformationen aktualisieren oder Feedback zu den Produktabbildungen geben?
Ist der Verkauf dieses Produkts für Sie nicht akzeptabel?
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. Contents same as US/UK editions.
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
There is one thing I don't like though and that is a pity: The author states that he has a strong Java background and just ported the code from his previous book to C# and labeled it as such to gain the attention of the .NET programmers out there. While that certainly worked for me, it took not long to realize that he is really not a native "sharper". The code examples constantly deny common naming conventions (e.g. interfaces in C# always begin with the letter I; we have lambda expressions...) which makes them hard to read and also makes the author somehow untrustworthy, especially when he is talking about clean code and refactorings.
Given that, I would definitely recommend the book to learn about agile principles and concrete design patterns but not for new C# programmers and not as a code reference.
Liest sich sehr kurzweilig und ist inhaltich absolut empfehlenswert.
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
I've read just about every review of this book and all the people who rated this book low (3 and lower) completely missed the entire essence of why this book was written. Their complaints were "not enough C#" and "how dare you not use generics, C# programmers should know better!" This book is not about teaching you how to program in C#; there's a ton of print out there to do that. This book is about teaching you how to approach coding, and what they teach can be applied to just about any language out there (well, OO is probably more suitable).
I've been coding professionally for 13 years and 8 more as a hubby before that. I've written some really, really horrendous code, and I got to where I am today by always reflecting back on all of my work. Over time I learned what to do and what should be avoided and when I first discovered Gang of Four's design patterns book, every single pattern I've already used somewhere in my own code.
Currently being a technical team lead on the project, I'm now brushing up on a lot of material regarding design, agile practices, architecture and so on. My goal is not to teach the team solely from my self-taught know-how. Instead, I'm reading all these books because I want to combine my experience with more authoritative voices on the subject and the views of other, more-experienced engineers.
Most of this book was nothing new to me. I've been already practicing a lot of the techniques and habits that the author recommends. However, having said that, there are still quite a few things that authors helped me see in a different light and I've already taken these lessons back to the team. No matter how much experience you have, if you read this book (keeping open mind and not with goal of learning C#), you will learn at least one valuable thing which will make you a better software engineer. They also helped me because their wording and examples are at a perfect level. Intermediate to experienced programmers (i.e. those with enough experience to know how much bad code really costs, in terms of money, time and blood pressure) can easily relate to what is being said and the examples they use are not standard, fictional, non-realistic "animal, cat, dog". Their examples helped me communicate with other team members to whom I wanted to convey some of the concepts behind agile, OOD approach and SOLID principles.
The final two sections cover a real-world case study implementation of a payroll system. Here the rubber meets the asphalt: walking through use cases, building transactions based on smartly-chosen patterns, discussion of what patterns make sense where and why, implementation, packaging, and evolution.
I found myself shaking my head in wonder as I read this book and stumbled across one nugget of gold after another. Some bits of goodness pop out in the middle of nowhere simply because the authors are so well-versed in their domain that they're letting fly wisdom even when discussing other topics. An example of this is in the XP pairing session episode where some discussion of increment operator side effects is tossed in the middle of another discussion stream. You read that section once and pass over it, only to do a head check, bounce back and re-read it while nodding your head and saying "Yeah, that's absolutely right and I might not have caught that otherwise."
Another bit of greatness is the chapter on UML. The authors are emphatic about keeping UML tightly in check and using it only in specific cases where it makes clear sense. Mountains of UML diagrams are not the answer; the authors show where a few concise diagrams make perfect sense.
More goodness can be found throughout the book in the gems relating to any number of design issues such as a small example of a problem the authors put forth to students of their various design/patterns courses: build a coffee maker. The authors go through the most common result they see and show the specific problem areas of that solution -- and then show a solution that is amazing in its simplicity, elegance, and maintainability.
This book is a critical read for folks at any level of experience. I'm going to do my best to make sure it gets on the required reading list for developers at my company.
Now for the bad news. One unnecessary oversight is the use of casts and "object" in some examples. Any author writing any C# book since 2005 must know that these idioms should no longer be encouraged. It is unacceptable for a book published in February 2007 to possess this flaw.
Generics, used in moderation, result in cleaner code that is also type-safe, and usually performs better due to the absence of boxing/unboxing. The authors should consider posting alternative examples that favor Generic types and collections on their errata web page. If you purchase this book, you would be well-advised to review the examples with a bias against the use of casts and the word "object".
To be entirely frank, I don't see how other reviewers can justify a five star rating.
Section I, the description of the Agile methology is brief. This is obviously the intent of the author and agile is meant to be documenation-light. This section only consists of 100 pages. It's a quick read giving you everything you need to know to implement the Agile methodology in your team.
Section II, is titled "Agile Design". These chapters are high-level design principles with low-level examples and a thorough treatment of UML. This should have been split into two sections. This first, would be most useful for a beginner/intermediate developer to take their skills to the next level. The second part, is required reading/knowledge for any developer who needs to work with a team or who needs to plan a complex application.
Section III is presented as a case study. Under the guise of a desiging a payroll system, the authors present the most popular design patterns. This section depends on the previous sections and is a great example of the thought process of agile developers.
The book is well written and easy to read for intermediate to advanced developers. Beginning developers would stuggle with some sections. However, all levels would beneift from reading this book.
Reviewers and some programmers who are so turned on by words like "agile, patterns, etc.." will find though the title of the book contains the buzz words, the content of it is a farce.
I read this book and I was like "this is the same Robert Martin rehashed junk just translated into C#" [Not even a decent translation]. You'll find them also telling Microsoft developers how they shouldn't name interfaces with a capital I.
On the contrary, I am glad they did, I like to peruse my object browser and easily see the differences, it helps me a lot. Their pompous attitude is displayed in the preface trying to diss C# developers.
Don't get me wrong, I respect Java developers like Martin Fowler, Kent Beck, etc.. But they have intelligent things to say in their books and are not condescending.
This book has nothing of real importance, and the real thrust of agile practices and also of design patterns can be found in much better books by better authors and who know and leverage the power of C#. Wouldn't you rather learn these things from real professional .NET developers like Francesco Balena, Trey Nash, Juval Lowy?
These authors simply don't know C#, which is evident by the examples they present and the way they present it.
I know I sound harsh [and will take a lot of flack I'm sure by some newbie or even perhaps a few skilled] but this book does not deserve the praise it has been getting, plain and simple. It's not quite as bad as C# Design Patterns by James Cooper [which is pathetic, to say the least], but it is not good enough to buy from the lowest seller from Amazon.
My top recommended books:
1. "Accelerated C#" by Trey Nash
2. "Programming .NET Components" by Juval Lowy
3. "Test Driven Development in Microsoft .NET"
4. "Head First Design Patterns" [in Java but good]
5. "CLR Via C#" by Jeffrey Richter
6. "Code Complete" [Much better on practices then this book]
7. "Pro C# 2008 and the .NET 3.5 Platform" [Excellent]
8. "Framework Design Guidelines"
9. "WCF" by Juvy Lowy [Advanced stuff, but excellent]
10. "Pro LINQ Language Integrated Query in C# 2008"