The skills of an architect
We must note that you don’t have to be a god of the technology stack to become an architect. I find it helpful to have a broad perspective on software development, emotional intelligence, leadership skills, and coaching. More specifically, some general skills embody the “architect role”.
Comprehend both functional and non-functional requirements. Take a pragmatic view combining what the user/client wants, what are their needs.
In development and architecture, we work on establishing the best solution, but that doesn’t mean all risks are removed. You can choose the most remarkable and modern technologies, but the result is damaging when applied in the wrong context. Every technology choice comes with the need for awareness of both costs and advantages. Our job is to research and find the solution that brings the most value in the context of our application and to understand the risks. This also goes for tools/libraries.
...
