Agile Principles, Patterns, and Practices in C# and over one million other books are available for Amazon Kindle. Learn more

Vous voulez voir cette page en français ? Cliquez ici.


or
Sign in to turn on 1-Click ordering.
or
Amazon Prime Free Trial required. Sign up when you check out. Learn More
More Buying Choices
Have one to sell? Sell yours here
Start reading Agile Principles, Patterns, and Practices in C# on your Kindle in under a minute.

Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.

Agile Principles, Patterns, and Practices in C# [Hardcover]

Robert C. Martin , Micah Martin

List Price: CDN$ 78.99
Price: CDN$ 49.76 & FREE Shipping. Details
You Save: CDN$ 29.23 (37%)
o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
In Stock.
Ships from and sold by Amazon.ca. Gift-wrap available.
Want it delivered Wednesday, September 3? Choose One-Day Shipping at checkout.

Formats

Amazon Price New from Used from
Kindle Edition CDN $37.44  
Hardcover CDN $49.76  
Paperback --  
Save Up to 90% on Textbooks
Hit the books in Amazon.ca's Textbook Store and save up to 90% on used textbooks and 35% on new textbooks. Learn more.
Join Amazon Student in Canada


Book Description

July 20 2006 0131857258 978-0131857254 1

With the award-winning bookAgile 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.




Special Offers and Product Promotions

  • Join Amazon Student in Canada


Frequently Bought Together

Agile Principles, Patterns, and Practices in C# + Clean Code: A Handbook of Agile Software Craftsmanship + The Clean Coder: A Code of Conduct for Professional Programmers
Price For All Three: CDN$ 112.11


Customers Who Bought This Item Also Bought


Product Details


Product Description

From the Back Cover

With the award-winning bookAgile 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. Martinhas 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 Martinworks 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.


Inside This Book (Learn More)
First Sentence
Many of us have lived through the nightmare of a project with no practices to guide it. Read the first page
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index
Search inside this book:

What Other Items Do Customers Buy After Viewing This Item?


Customer Reviews

There are no customer reviews yet on Amazon.ca
5 star
4 star
3 star
2 star
1 star
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 4.3 out of 5 stars  35 reviews
54 of 64 people found the following review helpful
4.0 out of 5 stars Well done, with one exception April 19 2007
By G. Askew - Published on Amazon.com
Format:Hardcover|Verified Purchase
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 of 28 people found the following review helpful
5.0 out of 5 stars Critical work on design and development Dec 12 2006
By James Holmes - Published on Amazon.com
Format:Hardcover
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 of 14 people found the following review helpful
5.0 out of 5 stars Agile Methods and Practices clearly explained Oct. 31 2006
By William Barrett Simms - Published on Amazon.com
Format:Hardcover|Verified Purchase
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 of 10 people found the following review helpful
5.0 out of 5 stars great book, title a bit misleading Jan. 10 2012
By Dennis Mnuskin - Published on Amazon.com
Format:Hardcover|Verified Purchase
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 of 9 people found the following review helpful
3.0 out of 5 stars Interesting, but needs work July 23 2010
By Maccurt - Published on Amazon.com
Format:Hardcover
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!

Look for similar items by category


Feedback