Identifying well-written code

It is not easy to define whether code is well-written. The best practices described in Chapter 17, Best Practices in Coding C# 9, can certainly guide you as a software architect to define a standard for your team. But even with a standard, mistakes will happen, and you will probably find them only after the code is in production. The decision to refactor code in production just because it does not follow all the standards you define is not an easy one to take, especially if the code in question is working properly. Some people conclude that well-written code is simply code that works well in production. However, this can surely cause damage to the software's life since developers can be inspired by that non-standard code.

For this reason, you – as a software architect – need to find ways to enforce adherence to the coding standard you've defined. Luckily, nowadays, we have many options for tools that can help us with this task...