Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Clean Code in C#

You're reading from   Clean Code in C# Refactor your legacy C# code base and improve application performance by applying best practices

Arrow left icon
Product type Paperback
Published in Jul 2020
Publisher Packt
ISBN-13 9781838982973
Length 500 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Jason Alls Jason Alls
Author Profile Icon Jason Alls
Jason Alls
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Coding Standards and Principles in C# 2. Code Review – Process and Importance FREE CHAPTER 3. Classes, Objects, and Data Structures 4. Writing Clean Functions 5. Exception Handling 6. Unit Testing 7. End-to-End System Testing 8. Threading and Concurrency 9. Designing and Developing APIs 10. Securing APIs with API Keys and Azure Key Vault 11. Addressing Cross-Cutting Concerns 12. Using Tools to Improve Code Quality 13. Refactoring C# Code – Identifying Code Smells 14. Refactoring C# Code – Implementing Design Patterns 15. Assessments 16. Other Books You May Enjoy

Defining good-quality code

Good code quality is an essential software property. Financial loss, wasted time and effort, and even death can result from poor-quality code. High-standard code will have the qualities of Performance, Availability, Security, Scalability, Maintainability, Accessibility, Deployability, and Extensibility(PASSMADE).

Performant code is small, only does what it needs to do, and is very fast. Performant code will not grind a system to a halt. Things that grind a system to a halt are file input/output (I/O) operations, memory usage, and central processing unit (CPU) usage. Low-performing code is a candidate for refactoring.

Availability refers to the software being continually available at the required level of performance. Availability is the ratio between thetime the software is functional(tsf) to thetotal time it is expected to function(ttef)—for example, tsf=700; ttef =744. 700 / 744 = 0.9409 = 94.09% availability.

Secure...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at R$50/month. Cancel anytime