Software Architect Useless. In this mock system design interview Im interviewed by a software engineer from Microsoft. When great thinkers think about problems they start to see patterns.
Also Microsofts definition as per the link you provided are less than stellar. Abstraction layers in software are what architecture astronauts tell you to do. However An architect does need to have an holistic view of the system which developers often dont have.
While design is an activity concerned with local constraints such as design.
This is how we do it. The leading expert is. To keep things balanced here are 10 wonderful reasons why YOU should not become an Architect. Design patterns are very esoteric in software engineering Its also a very high-end word There seems to be a design pattern Our code and project can naturally become very reasonable and easy to expand and maintain But things are not so simple There is no silver bullet in software engineering.