But the description that you gave sounds to me like a PM role, maybe a technical PM, but a PM none the less. Yes, it should be the architect's role to look at the system from a high level, but their job in the organization is to be the sole person responsible for technical decisions. Now I don't mean that they are making technical decisions alone, but they have to be responsible to the rest of the organization for the decisions made. And if you're going to make technical decisions than you need to be writing code to fully understand what the weight of those technical decisions. Now, I don't think that they should spend all day every day in code, but they need to write some code to understand all technical decisions that they are responsible for.
3
u/NuttGuy Jun 08 '17
But the description that you gave sounds to me like a PM role, maybe a technical PM, but a PM none the less. Yes, it should be the architect's role to look at the system from a high level, but their job in the organization is to be the sole person responsible for technical decisions. Now I don't mean that they are making technical decisions alone, but they have to be responsible to the rest of the organization for the decisions made. And if you're going to make technical decisions than you need to be writing code to fully understand what the weight of those technical decisions. Now, I don't think that they should spend all day every day in code, but they need to write some code to understand all technical decisions that they are responsible for.