Architect ? Design Patterns
A friend of mine asked me the other day: "What do you think is best? Software Architect or Project Manager? One is software oriented, while the other is more people oriented" the point is that both need to know about software design patterns.
The architect has to know design patterns for obvious reasons, while the PM needs to know it in order to identify whether the architect's design is too far fetch or that design would help him in phase 2 of the project.
For those who've been in the software industry for some time, we might remeber some thing called DNA, and not from the biological meaning. As software , design petterns change from time to time and we have to keep up to date our inventory of known and used(!) design patterns.
A good architect is known by he's knowledge to mashup a collection of design patterns to solve the problem.
For those of you here's another (known) design pattern link : Design Patterns Bootcamp: Model View * Patterns