Practical tips for clean C#

I obsess over keeping code as lean as possible and removing absolutely everything that doesn't have an explicit purpose. Having worked with C# for many years, I see some unfortunate patterns repeat themselves. Here, I describe some practical tips on what to look for, what to avoid and how to fix it.

Embrace instability

We loathe downtime and failing services. We talk about how we can keep our code stable. How we can avoid instability. However, certain types of instability should be embraced.