The good Software Architect is first and foremost a Software Designer.
An Architect must be able to communicate designs, and sometimes lead from the back.
An Architect must push and mentor, not pull and dictate.
An Architect plays a fundamental role in team building, team understanding and mentoring.
In many cases, an Architect also provides the enthusiasm and direction and
is a buffer between managers and developers as they understand both sides.
But, I firmly believe that the most important aspect of being an Architect is being of a mind that deals with the "big picture".
I for one, am concerned with everything from patterns to code maintenance, from usability to product differentiation.
I conduct Gap analysis on products, componentizing for profit, design for completion and so on.
and interesting discussion went on at the server-side
Previous Topic
