What exactly is a "Software Architect"?
- by Boydski
I've seen a few posts that briefly touch on the subject but don't address the question directly. So please don't label this as a dup.
Having been independant/freelance for 5 years or so, and having also had plenty of exposure to perm positions, I've been exposed to many views on what an "Architect" really is.
As a result, I've coined the term, "One man's architect is another man's n00b", as it seems to be perpetually relative.
I've interviewed at mom-&-pop shops that didn't think I was worth a hill of beans. I've also interviewed at world-class consulting firms who thought I was incredible. Again, it all seems relative.
But what specifically makes a software architect a true "Architect"?