This book shows how to design software architecture through examples. The first chapter is expected background, defining terms and what architecture is. I liked the comparisons between physical architecture, musical architecture and software design.
I saw one comment on another blog related to this claiming that all developers should be architects. Would you agree that this is the case? Based on experience, I don't believe this is necessarily true. While anyone designing software is to some degree an architect, not all programmers need to be architects. Once an architect has set a style and assigned a module to some programmer, that programmer does not need to have design skills. At my company, new college graduates fall into this category typically. Sure the work needs reviewed to ensure the assignment is fulfilled, but the programmer does not have to worry about the big picture or creating standards, that is done by the architect.
Any comments?
Subscribe to:
Post Comments (Atom)
Hi,
ReplyDeleteI have to agree with the other comments. In my experience as a developer, architect and manager, I have since systems that fail miserably because the developer didn't see the big picture and didn't think in terms of maintainability, adaptability, etc. Not many organizations can afford to have an architect. And even as an architect, it doesn't mean they had the right level of experience/knowledge in designing different systems. In these cases, the product is at the mercy of the developer(s). Having this knowledge ahead of time can be benefit both the developer and the product in the long run.
Regards,
Hilla