Comments on: Architecture versus Code http://garrettvlieger.com/blog/2009/11/architecture-versus-code/ Thoughts on technology, programming, and the industry Fri, 11 Jun 2010 04:09:20 +0000 hourly 1 http://wordpress.org/?v=abc By: Simon Brown http://garrettvlieger.com/blog/2009/11/architecture-versus-code/comment-page-1/#comment-46 Simon Brown Thu, 19 Nov 2009 20:44:48 +0000 http://garrettvlieger.com/blog/?p=162#comment-46 <blockquote cite="#commentbody-45"> <strong><a href="#comment-45" rel="nofollow">Garrett</a> :</strong> As an architect, it’s a matter of understanding your development team along with the project requirements. An “architecture astronaut” may overlook these factors, and this ultimately impacts the final deliverable — working code — which is what Grady Booch summarized much better than I could. </blockquote> Agreed, there are many things that drive the architecture and that includes the available skill set.

Garrett :
As an architect, it’s a matter of understanding your development team along with the project requirements. An “architecture astronaut” may overlook these factors, and this ultimately impacts the final deliverable — working code — which is what Grady Booch summarized much better than I could.

Agreed, there are many things that drive the architecture and that includes the available skill set.

]]> By: Garrett http://garrettvlieger.com/blog/2009/11/architecture-versus-code/comment-page-1/#comment-45 Garrett Thu, 19 Nov 2009 16:52:38 +0000 http://garrettvlieger.com/blog/?p=162#comment-45 <a href="#comment-44" rel="nofollow">@Ithink </a> I agree that defining "complex" is not really possible. My point was simply that certain architectural patterns (IoC, MVC, etc.) may take less experienced developers extra time to learn and become effective in using. If the project timeline and scope do not support introducing new and more advanced frameworks, it might mean using a simpler design that accomplishes the same goal. In an ideal world, developers should take the time to learn and understand new concepts, but that isn't always possible within the time frame of a project. As an architect, it's a matter of understanding your development team along with the project requirements. An "architecture astronaut" may overlook these factors, and this ultimately impacts the final deliverable -- working code -- which is what Grady Booch summarized much better than I could. @Ithink
I agree that defining “complex” is not really possible. My point was simply that certain architectural patterns (IoC, MVC, etc.) may take less experienced developers extra time to learn and become effective in using. If the project timeline and scope do not support introducing new and more advanced frameworks, it might mean using a simpler design that accomplishes the same goal. In an ideal world, developers should take the time to learn and understand new concepts, but that isn’t always possible within the time frame of a project.

As an architect, it’s a matter of understanding your development team along with the project requirements. An “architecture astronaut” may overlook these factors, and this ultimately impacts the final deliverable — working code — which is what Grady Booch summarized much better than I could.

]]> By: Ithink http://garrettvlieger.com/blog/2009/11/architecture-versus-code/comment-page-1/#comment-44 Ithink Thu, 19 Nov 2009 16:30:26 +0000 http://garrettvlieger.com/blog/?p=162#comment-44 I stoped reading on: "The methodology and design patterns should not be overly complex" You can balance and an crete rules for code as much as you want. But in the end have to make it work with the people who need to work with that. And there it gets realy fast blury, because the defenition of "complex" is not something you can measure easily. Its actually hard to find common properties here where all paricipating people agree. regards I stoped reading on: “The methodology and design patterns should not be overly complex”
You can balance and an crete rules for code as much as you want. But in the end have to make it work with the people who need to work with that. And there it gets realy fast blury, because the defenition of “complex” is not something you can measure easily. Its actually hard to find common properties here where all paricipating people agree.

regards

]]> By: Sean R http://garrettvlieger.com/blog/2009/11/architecture-versus-code/comment-page-1/#comment-43 Sean R Thu, 19 Nov 2009 15:40:19 +0000 http://garrettvlieger.com/blog/?p=162#comment-43 Good post. I completely agree with it. The Booch qoute is beautiful. Good post. I completely agree with it. The Booch qoute is beautiful.

]]> By: gsempe http://garrettvlieger.com/blog/2009/11/architecture-versus-code/comment-page-1/#comment-41 gsempe Thu, 19 Nov 2009 13:19:16 +0000 http://garrettvlieger.com/blog/?p=162#comment-41 Very interesting article. Thank you. Very interesting article. Thank you.

]]>