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)

Questions

  1. What does API stand for?
  2. What does REST stand for?
  3. What are the six constraints of REST?
  4. What does HATEOAS stand for?
  5. What is RAML?
  6. What is Swagger?
  7. What is meant by the term well-defined software boundary?
  8. Why should you understand the APIs that you are using?
  1. What performs better—structs or objects?
  2. Why should you test third-party APIs?
  3. Why should you test your own APIs?
  4. How can you determine what tests to write for your code?
  5. Name three ways to organize code into well-defined software boundaries.