Agile Principles, Patterns, and Practices in C# und über 1,5 Millionen weitere Bücher verfügbar für Amazon Kindle. Erfahren Sie mehr

Jetzt eintauschen
und EUR 0,35 Gutschein erhalten
Eintausch
Möchten Sie verkaufen? Hier verkaufen
Der Artikel ist in folgender Variante leider nicht verfügbar
Keine Abbildung vorhanden für
Farbe:
Keine Abbildung vorhanden

 
Beginnen Sie mit dem Lesen von Agile Principles, Patterns, and Practices in C# auf Ihrem Kindle in weniger als einer Minute.

Sie haben keinen Kindle? Hier kaufen oder eine gratis Kindle Lese-App herunterladen.

Agile Principles, Patterns, and Practices in C# [Englisch] [Taschenbuch]

Robert C. Martin , Micah Martin
4.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)

Erhältlich bei diesen Anbietern.


Weitere Ausgaben

Amazon-Preis Neu ab Gebraucht ab
Kindle Edition EUR 25,95  
Gebundene Ausgabe EUR 43,95  
Taschenbuch --  

Hinweise und Aktionen

  • Sichern Sie Ihre Daten kostengünstig und sicher im europäischen Amazon Web-Services-Rechenzentrum. So einfach geht‘s


Kunden, die diesen Artikel angesehen haben, haben auch angesehen


Produktinformation

  • Taschenbuch: 768 Seiten
  • Verlag: Pearson; Auflage: 1st (2006)
  • Sprache: Englisch
  • ISBN-10: 8131713067
  • ISBN-13: 978-8131713068
  • Größe und/oder Gewicht: 24 x 18,4 x 3 cm
  • Durchschnittliche Kundenbewertung: 4.0 von 5 Sternen  Alle Rezensionen anzeigen (2 Kundenrezensionen)
  • Amazon Bestseller-Rang: Nr. 1.747.464 in Bücher (Siehe Top 100 in Bücher)
  • Komplettes Inhaltsverzeichnis ansehen

Mehr über den Autor

Entdecken Sie Bücher, lesen Sie über Autoren und mehr

Produktbeschreibungen

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?


In diesem Buch (Mehr dazu)
Nach einer anderen Ausgabe dieses Buches suchen.
Einleitungssatz
Many of us have lived through the nightmare of a project with no practices to guide it. Lesen Sie die erste Seite
Ausgewählte Seiten ansehen
Buchdeckel | Copyright | Inhaltsverzeichnis | Auszug | Stichwortverzeichnis
Hier reinlesen und suchen:

Kundenrezensionen

4 Sterne
0
2 Sterne
0
1 Sterne
0
4.0 von 5 Sternen
4.0 von 5 Sternen
Die hilfreichsten Kundenrezensionen
1 von 1 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Entwurfsprinzipen für Fortgeschrittene 29. August 2012
Format:Gebundene Ausgabe
Kernstück des Buches sind die SOLID-Entwurfsprinzipen, diese werden sehr umfangreich mit Beispielen abgehandelt. Außerdem werden die wichtigsten Entwurfsmuster (und ein paar anspruchsvollere) erklärt, und man lernt Design-Smells und ihre Refactorings kennen.
Liest sich sehr kurzweilig und ist inhaltich absolut empfehlenswert.
War diese Rezension für Sie hilfreich?
2 von 3 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Solid patterns from a Java programmer 9. Februar 2012
Von SimonW
Format:Gebundene Ausgabe
I recently read this book and overall enjoyed it. It gives explanations and lots of examples to common agile principles and design patterns. There is also a short chapter about the usage szenarios and syntax of UML. I especially like the chapter that describes a dialogue between two newbie agile programmers who try to test-drive a bowling score program.
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.
War diese Rezension für Sie hilfreich?
Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)
Amazon.com: 4.3 von 5 Sternen  35 Rezensionen
54 von 63 Kunden fanden die folgende Rezension hilfreich
4.0 von 5 Sternen Well done, with one exception 19. April 2007
Von G. Askew - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Verifizierter Kauf
First, this book is well written and presents information in a constructive manner. It is well thought out, and is not just another C#/OOP/XP book.

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.
25 von 28 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Critical work on design and development 13. Dezember 2006
Von James Holmes - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
This book is amazingly great from start to finish. All the basics of good agile development are covered clearly and sensibly in the first section: what agile is, how to go about it, why testing and planning are so critical, and where refactoring fits in all of this. Design and general patters are hit in the second section, again in a clear, concise, and sensible fashion -- and with common sense thrown in.

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.
13 von 14 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Agile Methods and Practices clearly explained 1. November 2006
Von William Barrett Simms - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Verifizierter Kauf
This book really covers two topics: Agile management methods and development practices used by agile team.

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.
9 von 10 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen great book, title a bit misleading 11. Januar 2012
Von Dennis Mnuskin - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe|Verifizierter Kauf
There are two things I would've changed about this book: 1) remove "in c#" from the title and 2) make it clear that all code examples are pseudo-code in a made up language that kind of looks like C++/Java/C#.

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.
8 von 9 Kunden fanden die folgende Rezension hilfreich
3.0 von 5 Sternen Interesting, but needs work 23. Juli 2010
Von Maccurt - Veröffentlicht auf Amazon.com
Format:Gebundene Ausgabe
This book is not a five. Full of bad code that does not use the full strength of C#. The concepts and ideas are excellent. The author in person is witty and very charismatic. It could have been a better book if he would have correctly converted it to C#. The examples are okay, but could have been better. Examples with squares and rectangles just don't do it for me. I will say the book did change my coding style. This realy is more theory, something to think about. I fear people will use the book and start implementing patterns for symptons they do not even have!
Waren diese Rezensionen hilfreich?   Wir wollen von Ihnen hören.
Kundenrezensionen suchen
Nur in den Rezensionen zu diesem Produkt suchen

Kunden diskutieren

Das Forum zu diesem Produkt
Diskussion Antworten Jüngster Beitrag
Noch keine Diskussionen

Fragen stellen, Meinungen austauschen, Einblicke gewinnen
Neue Diskussion starten
Thema:
Erster Beitrag:
Eingabe des Log-ins
 

Kundendiskussionen durchsuchen
Alle Amazon-Diskussionen durchsuchen
   


Ähnliche Artikel finden


Ihr Kommentar