Monday, March 19, 2007

What does it take to be a Software Architect?

I am not sure how this is becoming a fad now. foo + Architect = big bucks. I know there are some good people out there that have the Architect title, but some are just jargon heads. I think the best combination is to be a good decision maker and broad technical knowledge that knows how to speak the jargon.

I think I have worked on the technical and decision making side of things, however I think I got my head too deep into making things work that I got left behind with all this jargon stuff. I think I better read some more books, rather than reading more manuals and code.

I wonder what would I need to be a REAL good foo Architect...

No comments: