Architects should code
I came across a post of Michael Stal reasoning why architects should code. This is a hot topic! I'm still struggling to find my own view on this matter. On the one hand, I of course agree it is right and good help refine the core to obtain the more concrete, tactical design and to supervise its implementation. That is why, among other reasons, I think architects should act hands-on in the implementation process.
Let's bring in some nuance and another perspective that Michael hasn't considered to the argument. What is an architect? I always refer to skyscrapr's taxonomy of architecture disciplines in which the window of the architectural perspective has been set to: Solution Architecture, Infrastructure Architecture, Strategic Architecture, and Industry Architecture. I see myself as a Solution Architect and feel responsible for deciding which technologies to use and work very closely with developers to ensure proper implementation, share vision and help with process, tools, principles and standards.
Should I code?
I think the answer to why architects should code or not lies deeper. Food for thought:
"Leadership is not something you do to people but something you do with people"