This week's book giveaway is in the Reactive Progamming forum. We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line! See this thread for details.
Hi Fairlie. It's not really about the number of years or projects, it's about the depth and breadth of experience. Like many other developers, I started my career writing code and taking instruction from more senior people on the team. After a few years, I gained experience and gradually started taking on larger and larger design tasks, until I was the person responsible for the technical delivery of a software system. For me, the architecture role is a role that you evolve into. Since the software architecture role is a technical leadership role, the "soft skills" (confidence, influence, communication, motivation, etc) are also important too. This article that I wrote for InfoQ might help you answer your question -> http://www.infoq.com/articles/brown-are-you-a-software-architect
The problems of the world fade way as you eat a piece of pie. This tiny ad has never known problems: