Most architects get pushed toward deeper specialisation over time. I went the other way, and I’ve grown comfortable with the ambiguity that comes with it.
The word “polyglot” has drifted well beyond its linguistic origins. For me, it describes an approach that values breadth over depth in any single stack.
I’ve always been fascinated and reflecting about the peacefulness and the respect that emerges when watching some masters doing their professions.
So, I spent lately some years time observing and trying to see the world through their lenses and may be, and if I’m good enough, adopt their skills and get inspired to improve myself personally and professionally.
The role of the software architect remains a subject of considerable debate: it is vaguely defined, difficult to pin down, and sometimes leads to nonsensical responsibilities in certain job descriptions.
I will not discuss here the precise day-to-day responsibilities of an architect within a team or company, but I will attempt, through my experience, to describe some of the aspects and qualities that any architect should possess.