Q:

Getting to an application architect level

I have been a developer for approx 10 yrs. I want to know how can I consider myself to be an archtect level techie? How can  developer move from code level development, to architect?
I obviously want to move up the tech ladder, and architecture seems appealing.
A second question would be, how do I learn about application architecture (big picture), in terms of 3.5 framework?
Any advise is appreciated.

A:

There are two criteria for being a software architect:
(1) You have to call yourself one.
(2) You have to convince someone to pay you to architect software.
Everything else is just scaffolding. If you're good at "big picture" development and planning, try to sell yourself as an architect on your next job search. If someone buys it, you're an architect.

A:

At the risk of exposing myself to the nitpickers and word-parsers, 
Being an "Architect" means you have to be able to design software "Systems", consisting of multiple "components" working together in a loosely coupled way to solve some fairly complex business problem, and be able to "lead" or "mentor" other developers in constructing said system.
In addition to being expert on the technology(ies) necessary to solve the problem, this also means you have to be able to understand the business problem at issue, from a business perspective, and be able to communicate fluently about it both with the business domain experts (using their language) and with the developers who will be constructing the components (in their language)  

A:

Being an architect is nothing more than a state of mind. There are potentially bad connotations that come along with having status of Architect. Particularly because nobody can truly answer the question, "What is an architect?"
First and foremost... 

Does this mean one draws up solutions but does not really implement them? 

If so, that is something to work towards I guess... but how does one work towards it by just "drawing up solutions"? Practical experience is prerequisite and must. A truly good programmer ultimately has good problem solving skills. A good problem solver ultimately knows how to construct good solutions. 
In my opinion, if one focuses on becoming an excellent programmer, the problem solving skills naturally start to develop. It's unavoidable that this will get recognized. Once recognized, people will start to ask for opinions on the best ways to solve problem X. When one starts getting asked these types of questions, one inherently become an architect.
In corporate organizations, one can move up to this state of mind and potentially have a physical title (and potential pay) to represent this state of mind. But we must not forget that it requires ACTUAL development of good solutions to problems. This is what ultimately brings us to this state of mind. 
In the end, it's just a word that tells very little behind the person carrying the title.

