46 ms·
There are defined Architect roles when you work at large companies where the division of labor requires more specific roles. Like others have said, the focus s
by matt_s 11y ago
There are defined Architect roles when you work at large companies where the division of labor requires more specific roles.
Like others have said, the focus should be on the bigger picture of the overall system(s) and how they inter-relate.
As you move around in your career, look for roles where you have more say in how the system is designed in the beginning. Take on more responsibility in how different modules/components interact.
Also read up on design patterns - including the book Patterns of Enterprise Application Architecture by Martin Fowler (and read his blog/site too).
Much of architecture is focusing on the parts of the system that have high risk and making them less risky, usually these are the parts where the systems interact with each other.
- antoaravinth 11y agoThanks for your response. So its all about designing the system and reduce the riskness involved in system interactions?
- matt_s 11y agoSystem interactions tend to be where there are mis-communications or bugs in API and cause issues during development. Especially if you are building on another companies service. That isn't it though, there are the non-functional aspects of the system that the design will need to take into account. Things like scalability, performance, etc. For example, think of a SaaS application that handles taxes. How would you design the interactions with government systems & banks, how would security work and how would you handle performance? That's what I meant by risky areas - risk to the project success, areas that may not be well known in the solution yet and may be "moving targets". Writing out the software that implements the tax law is probably a daunting task but should be very well known (probably a giant if/else tree with basic math).