Adaptive Code via C#: Agile coding with design patterns and SOLID principles Paperback – 9 Oct. 2014

I really enjoyed reading this book. The author, Gary McLean, shares his experience and opinions and is easy to follow. Nothing is left to chance. The book is about Scrum and the SOLID principles with an emphasis on the later. While the book states that it assumes the reader to be an experienced developer it still goes into detail on what an interface is in C# (my guess is this is what happens when you have your mother review your book) -- this is the only redundant section in the book.Dependency injection (the D in SOLID) is in particular important to know when working with C#, because the Microsoft development community is particular fund of dependency injection frameworks. While the case is made for dependency injection, dependency injection frameworks are merely implied being the preferred solution (OK, dependency injection frameworks are preferable to poor mans dependency injection, defined for the occasion in the book). The Wikipedia page on the topic does list a number of disadvantages with dependency injection (see https://en.wikipedia.org/wiki/Dependency_injection#Disadvantages), so I would have liked the author to have defended is recommendations against this critique (or at least some critique).Anyway, I enjoy reading something that I can agree or disagree with. And this is what this books gives and on a high level. If you find the topics relevant, the book is really good reading.

Worth a spot on every .NET developer's bookshelf, a great book on advanced programming techniques. The book expects you to know enough C# code to come to deal with any problem and then goes through numerous patterns/principles/approach that you can use to make best use of the code you already have. The book is only 385 pages and I got it read in 10 days but I will have to re read it quite a few more times to make practical use of all the finer points. To be honest the code is a bit abstract but there was a bit more hands on in the final two chapters.If you do don't know SOLID, don't have a good mental picture of Scrum and are serious about programming then I would definitely recommend this book for you. BUT it does expect you to be at an experienced level. Its well written and interesting : )

Good, solid book covering C# code and highlights some of the points to consider when writing and refactoring code to SOLID principles. A worthy additional to any C# programmer's book-shelf. There is plenty of useful information contains in the chapters. The IoC and dependancies chapters are almost worth buying in their own right. Recommended reading even if you have been doing Agile design and development for a while there will be something to learn here.

After about 10 years of commercial programming I started to learn about SOLID design principals (and old set of principles from the eighties), it radically changed the way I code and the way I teach the programmers I manage.Therefore I was extremely eager when I saw this book available for pre-order. I purchased it on the day it was released and read it within 2 days. It is clear, concise and extremely practical. The role playing chapter at the end ties together everything you learn throughout the book - and the accompanying C# code that shows how SOLID patterns can be written into your code - along with showing you how to review C# code and spot anti-patterns is priceless.Thanks to the authors for getting this book right. I have read so many SOLID books which have failed to bridge the gap between theory and practical application, this one nails it!As an added bonus I learned a bit more about Agile development (the bits we've fallen short of in the past), for which I am very grateful.

Really liked the coverage of the principles, however I did not enjoy the scrum chapters using an imaginary team found this wasted my time. Would of like more investment into other design patterns.

There is fine line between knowing the SOLID principles and understanding the SOLID principles. This book explains each principle in dedicated chapters through code examples, code smells, practical design pattern inspired solutions and best practice in general. SOLID principles are appearing in job applications as standard knowledge for the mid-senior level developers, Gary shares his experiences to those who may not have a wealth of experience in coding but have nailed down the fundamentals and are looking to understand how to develop adaptable code in an agile development.

Excellent book on best practices on how to develop and architect SOLID projects. Well written and easy to understand and touches pretty much every best practice you need to know. Examples are in c# but the concepts are platform agnostic

I found the explanations to be very clear and well-written, but the book is very intense and doesn't hold you by the hand. I had to dedicate time to each chapter, read it multiple times and try and apply it practically before I could move on to the next concept. Basically it is a book for professionals.