Le Café Central de Deva
..... Deva blogs!!
I like the following excerpts which I liked from the interview: “you can copy and paste the code but are you know whether this is right to do in your context”, “architect should constant likely at the technical aspect of the project”. This is a great interview to catch if you're headed down this career path!
Click here to view the video:
Great post from two experienced minds. This article has focused on defining the characteristics of a software architect and importance of the role. Well done!!
Awesome video!! But i want to defer with couple of them. Some of the responsibilities mentioned above are sometimes not handled solely by the architect. Instead, they may be handled by a project manager, an interaction designer or a business analyst. That’s all good and well if you have those roles in your project. Any large project would. What I am trying to say is that you, as the architect, must continuously communicate with all of these functions (and certainly several more) to get to the form of your project. Some things you just have to know about your domain in order to be a good architect. One good thing to know is who your friends are in the organization. Everything that I’ve written above has to matter to you as an architect! You can’t be a great architect if you don’t honestly and truly care.