Any software project needs some standards and guidelines. These "conventions" can cover code style, architecture, best practices and common mistakes or issues.

All of these could be found in code reviews. but could also be easily missed. These are also the "easiest" to spot and real issues (business, logic, performance...) might go unnoticed.

In this talk we'll cover how we can automate detecting the easy stuff so we can focus on the hard parts. We'll be covering and automating the following items:
- enforce code styling
- verify architecturel conventions
- check best practices
- avoid mistakes

To do this we'll be implementing tips and tricks using:
- standard .NET tools
- architecture (unit) tests
- code analyzers and fixers
- build pipeline checks

All these enforcements are not to limit creativity but to remove wasted time and have more time for the creative or hard work.

This is suited for developers and architects who want to have more time for the creative part of our work.