Honestly, I think achieving architect status means that you've earned the right amongst your peers. Or you've earned the title by proving yourself within a job interview.
I don't think its winning the lottery. And to be honest, I don't think having the title "architect" really means anything either. I think as a developer,
Let me ask you this, why is it important for you to be an architect?
I guess we get confused somewhere in the middle. My question never was about a title. I asked how to gain knowledge (or experience) in most effective way and what kind of knowledge people consider to be most valuable (in sense of giving most insight).
Build stuff my friend. That’s it. Gain the knowledge by building stuff and leading teams. See what works and what doesn’t.
Seems like you want a simple answer like, if you read book X or blog post Y, it will tell you how to be a software architect. It takes real experience in the field of software development. You cannot skip all the hard work it takes to earn the badge.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.