I had many conversations with software engineers in various domains and disciplines during the past 20 years of my career as a software engineer and software architect. Some of them were senior engineers having 8 or 10 years of experience. Many of them were early in their career having 3 to 5 years of experience. Some of them were my colleagues. Some were job candidates. At some point, they all ended up with the same question that I heard over and over again:
“I want to become a solution architect. What are the resources to learn more about architecture?” — A question asked by many Software Engineers.
Well, they were asking the wrong question. You will know why if you read on. Also, since my company is hiring Lead Software Architects as of this writing, it is worth explaining what a Software Architect is and how to become one.
What is Software Architecture?
What is software architecture in the first place? As the Software Architect title implies, a common analogy that I often hear is the construction of a building. The building architect creates the blueprint of the building. The engineers build it physically and make it work according to the blueprint. I would argue that this is a poor analogy in multiple ways.
