Take the tour ×  There have been many questions with good
answers about the role of a Software Architect (SA) on
StackOverflow and Programmers SE. I am trying to ask a slightly
more focused question than those. The very definition of a SA is
broad so for the sake of this question let's define a SA as
follows:  A Software Architect guides the overall design of a
project, gets involved with coding efforts, conducts code
reviews, and selects the technologies to be used.  In other
words, I am not talking about managerial rest and vest at the
crest (further rhyming words elided) types of SAs. If I were to
pursue any type of SA position I don't want to be away from
coding. I might sacrifice some time to interface with clients
and Business Analysts etc., but I am still technically involved
and I'm not just aware of what's going on through meetings.
With these points in mind, what should a SA bring to the table?
Should they come in with a mentality of "laying down the law"
(so to speak) and enforcing the usage of ce