Agile Principles, Patterns, and Practices in C#

Testo che pur nella sua essenza di materiale tecnico si lascia leggere con piacere.

Thanks. Book in great shape and great packaging.

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.

I have a bookshelf groaning with books on C# and agile software development. This is without doubt the best I've read. Robert Martin has somehow managed to distil his experience of many years into one cohesive tome, which is easy to read and provides practical advice on all aspects of development - agile, TDD, UML and design patterns.As for the previous reviewer who gave this a ludicrous 1 star review and suggests the GOF as a better alternative, I would suggest that he is either an abstract genius, or has never actually read the GOF stuff and is just name-checking this in a poseur like fashion!For the rest of us, this is probably as good as it gets.

You can never go wrong with Robert C Martin. Although I am not using C# these days, most of the examples are universal.