System Architect life
Note
Architects keep a lot in their minds, so being able to operate at different levels of abstractions is a necessary skill.
An example of that is, Being able to talk about code quality requirements at a very deep level in terms of non-functional requirements like code coverage and unit tests, while also being able to talk about high level stuff like inter-system interactions in a large company.
So different Architects get together to talk about how entire groups of systems interact together and have different kinds of meetings and conversations on how these interactions occur, since they have different kinds of ideas/artifacts.
Architects are Agents of change, and they keep different kinds of perspectives in their mind:
Architects also need to be up-to-date with the trends/market for new ways or tools to solve problems, and this introduces a technological risk which is one of the biggest challenges an architect faces.
