Clean Code in C#: Refactor your legacy C# code base and improve application performance by applying best practices

A must for any developer.

The author takes great pains to talk about code review and the importance of coding standards and lays out rules of thumb (such as methods should be 4 lines or less) with great authority. Then he gets totally in the weeds with threading and concurrency - which is a topic for someone who doesn’t need definitions for Dependency Injection. Although I’m sure the author is a fine programmer, I wish he had spent more time on detail and fully fleshed out examples and less time with introductory bullet points, a full summary and questions for each chapter. It’s like he’s trying to appeal to all levels of programmer in one book.

Disclaimer: I was provided with a free copy of this book, but the below is my objective review of the bookThis book "Clean Code in C#" is a veritable tome on best practices on writing good software.It starts right off with a comparison of good vs. bad code and then delves into the basics such as:- Coding standards (and the need for one)- SOLID principles- Exception Handling- Unit & End-to-End testingIt then tackles Advanced topics such as:- Threading & Concurrency- Designing and Securing APIs- Cross-cutting concerns- Tools to improve Code QualityThe best gem is the last chapter that deals with Code Smells at the Application, Class and Method level. There is also an additional chapter on implementing creational and structural design patterns.If the reader weren't to practice any what is written, it is certainly good food for thought and practices that one can use as your skills mature.

I really liked this book it had good information! I recommend to read it for sure! Good advice on how to refactor coding! it helped me a lot since I am a software engineer.

Contenu parfait, j'aurais aimé qu il soit imprimé en

Nice code examples, it discusses main issues regarding to C#

The media could not be loaded.  I wasn't sure who the author was aiming the book at - but if anything I'd say an intermediate level C# coder who has just been asked to review others' code.The first few chapters covered general advice (with good examples) on good code and bad code and were pretty easy but well-explained and I still learned things and it reinforced what I thought I knew and gave me the vocabulary to explain it.Towards the back, he seemed to veer into different territory with chapters on threading and concurrency and design patterns (2 subjects I always find difficult to understand as I rarely use either) but I really appreciated his chapter on walking through an example of how to secure APIs - again doesn't seem relevant to clean coding particularly but I have found it hard to find good examples of this elsewhere.His chapters on unit-testing and refactoring were great. All-in-All a good purchase and I'll read it again sometime.I prefer to study from tree-ware (I spend way too much time in front of a screen already) and I like underlining stuff in books as it helps me learn so I've added a quick video to show the book after I've finished.

Ich bin Softwareentwickler mit über 10 Jahren Erfahrung und war auf der Suche nach einem Buch, das speziell auf die Umsetzung der Clean Code-Prinzipien in C# eingeht. Anfangs war ich total begeistert, aber das ließ nach den ersten Kapiteln nach, weil ich ständig über logische, Schreib- oder Codefehler stolperte.Ein Beispiel: Der Author zeigt einen Code mit einem nicht instanziierten Klassenobjekt, auf dessen Eigenschaften trotzdem zugegriffen wird. Laut dem Autor sei es "klar, dass hier eine ArgumentNullException" geworfen wird. Ein erfahrener Entwickler weiß aber, dass stattdessen eine NullReferenceException geworfen wird. Allgemein werden im Buch sehr oft verschiedene Typen von Exceptions durcheinander geworfen.Auch die Kapitel sind von meinem Gefühl her sehr willkürlich gewählt. Ich kann mich einer anderen Rezension, die ich gelesen habe, anschließen: Threading hat nichts mit Clean Code zu tun.