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 do you call a method that has no parameters?
  2. What do you call a method that has one parameter?
  3. What do you call a method that has two parameters?
  4. What do you call a method that has three parameters?
  5. What do you call a method that has more than three parameters?
  6. What two method types should be avoided and why?
  7. In layman's terms, what is functional programming?
  8. What are some advantages of functional programming?
  9. Name one disadvantage of functional programming.
  10. What is WET code, and why should it be avoided?
  11. What is DRY code, and why should you use it?
  12. How do you DRY out WET code?
  13. Why should methods be as small as possible?
  14. How do you implement validation without having to implement try/catch blocks?