Comments on: Jelly belly of an architect http://brainsnorkel.com/2004/12/16/how-do-you-define-software-architecture/ Manifesto-driven development. Eclectic thoughts. Tue, 14 Feb 2012 13:12:08 +0000 hourly 1 By: Alan Green http://brainsnorkel.com/2004/12/16/how-do-you-define-software-architecture/comment-page-1/#comment-138 Alan Green Wed, 22 Dec 2004 03:12:16 +0000 http://brainsnorkel.com/?p=32#comment-138 Excepting the Matrix, most Architects I've seen have been the people most repsonsible for providing the over-arching technical vision, and seeing that the vision is implemented where it can be and modified when it can't be. At the start of the project, when requirements are vague and the technology unclear, everybody is looking to the architect to show the way. But once the way is defined, their utility diminishes quickly. You can tell a really good architect because halfway through the project, the project manager asks him to please stop being visionary around his developers and to please go play golf or something. Excepting the Matrix, most Architects I’ve seen have been the people most repsonsible for providing the over-arching technical vision, and seeing that the vision is implemented where it can be and modified when it can’t be. At the start of the project, when requirements are vague and the technology unclear, everybody is looking to the architect to show the way. But once the way is defined, their utility diminishes quickly.

You can tell a really good architect because halfway through the project, the project manager asks him to please stop being visionary around his developers and to please go play golf or something.

]]>