Considering the architect's role distinct from the developer's one is a residual of the building metaphor applied to software development. Personally I find it difficult to consider the architect's role as distinct from the developer's one. In my opinion a so-called architect should be an experienced developer able to see the (infra)structure of a system from an higher level and able to make decisions in order to solve a problem and guarantee some non explicit requirements (maintainability, security, readability, reusability, etc.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Considering the architect's role distinct from the developer's one is a residual of the building metaphor applied to software development. Personally I find it difficult to consider the architect's role as distinct from the developer's one. In my opinion a so-called architect should be an experienced developer able to see the (infra)structure of a system from an higher level and able to make decisions in order to solve a problem and guarantee some non explicit requirements (maintainability, security, readability, reusability, etc.)