If you don't program you have no business doing architecture. It's a fallacy to believe you can be in tuned with the needs of software without being involved in it's writing and deployment .
There's no way you can understand the needs of a database without being strongly aware of how the database is used. There's no way you can understand the needs of a load-balancer without being acutely aware of how the backend software works.
Architecture designed absent the programming element will inevitbly be the wrong architecture. This applies to any kind of administration and deployment. These are all under the same hood of software development.
Now, you might think that you're well enough informed that you can make appropriate decisions. The truth is that if a programming time can summarize and communicate the requirements clearly enough to an architect, they simply don't need the architect, somebody on the team can do it themselves. Architecture is not a role that requires excessive specialization.
If you still don't think this applies, then perhaps your role is more of a product manager and not an architect at all.
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.
If you don't program you have no business doing architecture. It's a fallacy to believe you can be in tuned with the needs of software without being involved in it's writing and deployment .
There's no way you can understand the needs of a database without being strongly aware of how the database is used. There's no way you can understand the needs of a load-balancer without being acutely aware of how the backend software works.
Architecture designed absent the programming element will inevitbly be the wrong architecture. This applies to any kind of administration and deployment. These are all under the same hood of software development.
Now, you might think that you're well enough informed that you can make appropriate decisions. The truth is that if a programming time can summarize and communicate the requirements clearly enough to an architect, they simply don't need the architect, somebody on the team can do it themselves. Architecture is not a role that requires excessive specialization.
If you still don't think this applies, then perhaps your role is more of a product manager and not an architect at all.