Book Image

Clean Code in C#

By : Jason Alls
Book Image

Clean Code in C#

By: Jason Alls

Overview of this book

Traditionally associated with developing Windows desktop applications and games, C# is now used in a wide variety of domains, such as web and cloud apps, and has become increasingly popular for mobile development. Despite its extensive coding features, professionals experience problems related to efficiency, scalability, and maintainability because of bad code. Clean Code in C# will help you identify these problems and solve them using coding best practices. The book starts with a comparison of good and bad code, helping you understand the importance of coding standards, principles, and methodologies. You’ll then get to grips with code reviews and their role in improving your code while ensuring that you adhere to industry-recognized coding standards. This C# book covers unit testing, delves into test-driven development, and addresses cross-cutting concerns. You’ll explore good programming practices for objects, data structures, exception handling, and other aspects of writing C# computer programs. Once you’ve studied API design and discovered tools for improving code quality, you’ll look at examples of bad code and understand which coding practices you should avoid. By the end of this clean code book, you’ll have the developed skills you need in order to apply industry-approved coding practices to write clean, readable, extendable, and maintainable C# code.
Table of Contents (17 chapters)

Mutability, immutability, and thread safety

Mutability is a source of bugs in multi-threaded applications. A mutable bug is normally a data bug caused by values being updated and shared between threads. To remove the risk of mutability bugs, it is best to use immutable types. The guaranteed safe execution of a body of code by multiple threads at the same time is called thread safety. When working with multi-threaded programs, it is important that your code is thread-safe. Your code is thread-safe if it removes race conditions and deadlocks, along with problems caused by mutability.

An object that cannot be modified after it has been created is an immutable object. Once created, if passed between threads using correct thread synchronization, all threads will see the same valid state of an object. Immutable objects allow you to share data safely between threads.

An object that can be modified after it has been created is a mutable object. Mutable objects can have...