Strategic thinking

Continuing the idea that not everything labeled as quality is what you need, I would like to discuss best practices. Again, weigh the complexity of your system, the time you invest in some “best practices” versus the advantages they bring, the time you have to invest versus the time it saves, and the constraints of your environment.

Principles, of course, were defined for a good reason after trying and failing in specific scenarios, but that doesn’t mean that they are applicable in all systems. When the essential principles are clear and well-weighted, everyone in the team should be aware of them and ensure everyone is going in the same direction and is on the same page. Maybe you will find it hard to decide on that list of principles because the system’s context is sometimes too complex and hard to follow up in the smallest details. The feedback from the team will help you as an architect determine whether some principles were applicable...