Clean Code in C#: Refactor your legacy C# code base and improve application performance by applying best practices
M**D
Easy read
A must for any developer.
C**N
Contenu parfait, j'aurais aimé qu il soit imprimé en couleur.
Contenu parfait, j'aurais aimé qu il soit imprimé en
H**I
Covers Important issues
Nice code examples, it discusses main issues regarding to C#
G**E
Really enjoyed this book
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.
M**Y
Audience Not Well Targeted — Book Should Have Been Refactored into Multiple Books.
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.
Trustpilot
2 weeks ago
3 weeks ago