http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html One of the things that I mention every time I do training or mentoring around technical architecture is that you don't just wake up one day and become a TA. From my experience, it's much more of an evolutionary path where you gradually take on more and ... en Simon Brown Thu, 04 Jun 2009 08:24:31 GMT Pebble (http://pebble.sourceforge.net) http://backend.userland.com/rss http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comment1244103871798 Completely depends on the project. If you have a strong team of develpers and they can carry out the vision themselves it is not necessary. Keep in mind that each programmer in this case must have a specific role and there must be a healthy communication between the team. If you hire a software architect it will be alot easeit to explain your vision to one person and have him do all the organizing and orchastrating. Hope thi helps!! Yavar Anonymous http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comments http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comment1244103871798 Thu, 04 Jun 2009 08:24:31 GMT http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comment1170280419824 hello there, my name is Jorge Luis Ayala .. and basically i just want to know if anyone is affiliated or knows what you need to become a architect? Becuase i would like to become a future worker.. so please if you know anything can you reply because i am ascertaned to know please.. well thanks for you time and hopefully yall will response.. jorge luis ayala http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comments http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comment1170280419824 Wed, 31 Jan 2007 21:53:39 GMT http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comment1163560624624 <p>No. We don't need another architect. </p> <p>Traditionally an architect would design the whole building before giving the plans to the builders. In IT the word also carries a lot of BUFD baggage, an approach I am not interested in unless said architect carries a working crystal ball.</p> <p>I think an architect is a combination of roles. If the architecture evolves then they can help guide that evolution. They can be a technical lead, tutoring the team and offering advice when things get tough. They can guide the client through the development process and help understand their requirements. They han help recruit new team members. </p> <p>They cannot go into hibernation and produce an 'In-theory-this-plan-will-solve-all-our-problems-for-evermore' document. </p> Mike http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comments http://www.codingthearchitecture.com/2006/10/25/do_you_need_an_architect.html#comment1163560624624 Wed, 15 Nov 2006 03:17:04 GMT