Myth no.2: Only the architect cares about architecture

I believe that making coding a part of your role as an architect is a game-changer. I’ve worked in teams where the architect opened the IDE and started coding, and I’ve worked in groups where the architect was only a title; I almost had no idea who that was, and I met them only when I was building a feature that impacted the architecture. From my experience, an architect that stays close to the team becomes naturally more engaged with the team and, as a result, understands the impact of the architectural decisions and the reality of the existing code base that tries to fit those decisions. I was lucky enough to be part of a team where the development team was consulted regarding some necessary architectural changes. The architect wanted to validate his architectural perspective in real-life scenarios and with people who would implement his vision in the end. At the same time, by having this kind of team discussion...