What does the title System Architect really mean? What do you need to know to be a system architect. Do you need to know design patterns or something like that? At work we have a couple so called "System Architects". They do the same stuff as we developers, but the distinction are that they are older and thus has more experience and knowledge of the business domain we work in. But I'm not really seeing the architecting side of work really...
closed as not constructive by Robert Harvey, Telastyn, GlenH7, jk., Caleb Oct 17 '12 at 16:22
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
You might have seen Spiderman - With Greater Power comes Bigger Responsibilites. You can say the same when a SD becomes a SA.