Software architect is a job title, meaning if you want to become one: start acting like one!
Someone already mentioned knowing the requirements and doing business related conversations but that's part of the software architect role.
There are many other important stuff as well:
An end-to-end knowledge about building/testing/deploying systems.
Given point #1, you will be the focal point in your team, so you will help the others with anything that comes up.
By anything, I do mean it literally; it could be designing the database, or could be fixing a deployment pipeline, or even showing a frontend dev how to fix a UI bug.
Knowing various programming languages, programming paradigms, design patterns, software design approaches (ddd, tdd, bdd... all kind of D's), and a handful of architectural styles and patterns.
Practical knowledge of distributed systems and its related parts, like: networking, service oriented architecture, and caching.
Willing to learn all the above on a daily basis!
I believe CS courses won't really help as much as learning from exceptional devs, some names that come up to my mind: Martin Fowler, Uncle Bob, Greg Young, and Udi Dahan.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Software architect is a job title, meaning if you want to become one: start acting like one!
Someone already mentioned knowing the requirements and doing business related conversations but that's part of the software architect role.
There are many other important stuff as well:
An end-to-end knowledge about building/testing/deploying systems.
Given point #1, you will be the focal point in your team, so you will help the others with anything that comes up.
By anything, I do mean it literally; it could be designing the database, or could be fixing a deployment pipeline, or even showing a frontend dev how to fix a UI bug.
Knowing various programming languages, programming paradigms, design patterns, software design approaches (ddd, tdd, bdd... all kind of D's), and a handful of architectural styles and patterns.
Practical knowledge of distributed systems and its related parts, like: networking, service oriented architecture, and caching.
Willing to learn all the above on a daily basis!
I believe CS courses won't really help as much as learning from exceptional devs, some names that come up to my mind: Martin Fowler, Uncle Bob, Greg Young, and Udi Dahan.