Saritha Penumudi wrote:Quick question on technology selection from article http://www.infoq.com/articles/brown-are-you-a-software-architect. As there are more than one possible solution/problem for every problem, How would you go
about picking one technology/framework over other. It can get overwhelming to try out (do POC) on each framework to see if it fits the solution.
Are there better tools or process that makes this selection easier?
K. Tsang wrote:Another question based on this is to become a software architect (or another other architect), how technical (depth) does one need and in how many topics? Eg programming xyz, design pattern, framework abc, app server pqr, etc There are so many products or technologies one can delve on. And at the same time, one can't be expert at everything.
On the contrary, for the breath, being aware of such and such technology but not knowing what its purpose or benefit would be like not knowing it at all. But when one start researching/learning it the depth mode may take over. How much is enough for breath?
Burk Hufnagel wrote:I don't know about a system architect, but I do believe that a software and solution architects should have a background in programming - and keep up with what's new in the languages they're designing for; otherwise how will they know that their solutions will work?
charlsy chuks wrote:On the other hand with regards to tools and patterns, when the architect does not know much about a pattern like MVC and his team members are equally green horns but he insists MVC must be used because of the benefits, I think you have a recipie
for trouble because initially the team will be slow (opposite of agile) as they will be learning new stuff and coding at same time.
Junilu Lacar wrote:Coming from anyone else, saying that the book is "theoretical" would be a disservice -- I would go with "philosophical" instead. You discuss a number of things that architects should do based on your own values and beliefs as a software developer: "Architects should code," "Architecture should be 'just enough'," "Architecture is a role, not a rank" to cite just a few. IMO, these are key foundational values and principles that guide all the other aspects of an architect's work.
Jayesh A Lalwani wrote:In my last job, I eventually became the "chief architect". I'm like dude!! stop giving me bullshit titles. I "demoted" myself to technical architect