My 2 Cents

Part I of this article described the various types of software architect. In this article we’ll describe the work they do, or should do, in a bit more detail. continue reading…

What does an architect do?  This surely won’t be the last time this question is asked on this forum.  It is an important question, and somewhat hard to pin down; especially when one considers the many titles of a Software Architect. There seems to be a general idea of what a software architect does, but many software managers don’t seem to believe the role is necessary, or even distinct: “Can’t we just have one of our senior developers do that?”  Sure you can; If you have a senior developer who possesses those skills. continue reading…

Okay, that’s a bit strong, but it got your attention. In truth, I think design patterns are very useful things. They can aid in understanding software design, for documenting and communicating design, and for applying to or refactoring designs; but many people see them as something more.  I saw a consulting job requirement a while ago, and one of the required skills was that the candidate “must have used ALL of the design patterns” documented in the GoF Book.  Is this really significantly different than requiring that a building architect has applied every form of archway and flying butress ever used in the history of construction?  Isn’t awareness more important than past application? continue reading…