Practical .NET Coding Guidelines We Use Internally

We’ve been standardizing .NET practices across multiple teams and kept running into the same issues: inconsistent conventions, hard-to-review code, and “style debates” that slow delivery.

This repo captures the coding guidelines we actually use in practice: focused on readability, maintainability, and avoiding common .NET foot-guns.

It’s intentionally opinionated but grounded in real-world usage. Feedback and counter-examples welcome.