Book Image

Improving your C# Skills

By : Ovais Mehboob Ahmed Khan, John Callaway, Clayton Hunt, Rod Stephens
Book Image

Improving your C# Skills

By: Ovais Mehboob Ahmed Khan, John Callaway, Clayton Hunt, Rod Stephens

Overview of this book

This Learning Path shows you how to create high performing applications and solve programming challenges using a wide range of C# features. You’ll begin by learning how to identify the bottlenecks in writing programs, highlight common performance pitfalls, and apply strategies to detect and resolve these issues early. You'll also study the importance of micro-services architecture for building fast applications and implementing resiliency and security in .NET Core. Then, you'll study the importance of defining and testing boundaries, abstracting away third-party code, and working with different types of test double, such as spies, mocks, and fakes. In addition to describing programming trade-offs, this Learning Path will also help you build a useful toolkit of techniques, including value caching, statistical analysis, and geometric algorithms. This Learning Path includes content from the following Packt products: • C# 7 and .NET Core 2.0 High Performance by Ovais Mehboob Ahmed Khan • Practical Test-Driven Development using C# 7 by John Callaway, Clayton Hunt • The Modern C# Challenge by Rod Stephens
Table of Contents (26 chapters)
Title Page
Copyright and Credits
About Packt
What to Know Before Getting Started
Files and Directories
Advanced C# and .NET Features

Changes to Speaker Meet

Change is inevitable with any application. Requirements change as a result of a new business rule, feature enhancement, discovery and remediation of a defect, and so on. Change is especially certain when test driving an application. Luckily, through the process of TDD, your application should be easily and safely modifiable.

If a system is loosely coupled, then changes to one part of a system should, in theory, have little to no impact on the rest of the system. A comprehensive suite of unit tests should alleviate the fear of making changes.

Unfortunately, the tests are only valid for the scenarios which they define. If sufficient tests aren't written to cover certain scenarios or edge cases, then it is certainly possible that a bug could find its way into production. If the TDD approach is not taken, or worse, tests aren't written at all, then you may discover that it is quite easy for a bug to make it through all of the checks of your code review process and CI/CD...