I just ran across Ryan Plant's post about the "Web Architect." He seems affronted at the idea, but this was one of my titles in a former life. So it's not so surprising to me. There are indeed a lot of considerations (some of which Ryan talks about) that you have to think about when designing web applications that you don't have to think about in other kinds of applications. It really does take a specialized set of skills.
That said, I don't think that having those specialized skills would necessarily qualify one as a web architect. Given my previous thoughts on the subject (illuminated here and elsewhere), many of which seem to echo or be echoed in other publications on the quesiton of what is IT architecture, I tend to think that the web architect role would be a valid role if it was thought of as the individual responsible for a company's web presence. There are I think distinct questions that have to be thought about in terms of the business and how it is represented on the web (at least on the properties controlled by the business).
Depending on the company, there may be warrant to have an individual in a web architect role, which would of course assume the knowledge of the specific skills Ryan speaks to, but, more importantly, this role would be responsible to consider how to strategically take advantage of the web to address business needs. In some companies, such a role may be subsumed into the greater enterprise architect or solutions architect roles, but in others, I could see it being a peer or possibly a report to the enterprise architect and a peer with other IT architects, working with him to coordinate technology application for the business specifically on the web. This assumes that there is sufficient business need for such a distinguished role, not just a need for the web skill set.
The opinions expressed herein are solely my own personal opinions, founded or unfounded, rational or not, and you can quote me on that.
Thanks to the good folks at dasBlog!
Copyright © 2017 J. Ambrose Little