Best practises and pragmatism

Patterns and best practises in software development world are mythical words that inspire fear.
Seriously they give control, common language and blablabla further following a book.

Pragmatism is important in the world of architecture.
We need to find the most efficient solution that satisfies requirements (functional and non-functional).
What is the most efficient solution today can be not so tomorrow. Welcome to the rainbow world of software architecture.

Tuning architectural solution to comply patterns and best practises leads it further from an efficient solution of requirements.
Business pays when it's happy and calm, not when it's stressed with pink clouds of best practises that it doesn't even understand.

What is an architecture of complex and distributed system?
Tons of stuff. There are monolith and microservices, Severless and even driven approaches, plugin system and legacy that is forbidden to touch.

When I hear about patterns and best practises while discussing rationale of a solution, I know the person was a developer yesterday.

Let's be pragmatic.