I'd say on this site the overwhelming answer will be: "Yes".
The overwhelming answer in industry is: "No". Their perspective is architects get paid multiples of what they pay a software developer, so they should get much more out of them.
I don't think there's a simple cookie-cutter answer. You have to do what's most effective both in the short and long term.
Short Term
In the short term, as an EA, you have to do whatever it takes to get the project moved along. Sometimes you're doing prototyping, project management, daily war rooms, bug bashes, integration work. And yes, much of it is being a great communicator and "force multiplier," getting dozens or hundreds of people on the same page.
Let's further acknowledge: That is both thankless and it eventually makes you useless. How do I know? I was that guy.
Long Term
Longer term, you need to rotate yourself back through development, whether that's a new assignment with your company, or a new gig entirely. Own something. Take it to production. Sustain it. This is how "architects" stay relevant.
Call it a "sabbatical" if you must, but do it.
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.
I'd say on this site the overwhelming answer will be: "Yes".
The overwhelming answer in industry is: "No". Their perspective is architects get paid multiples of what they pay a software developer, so they should get much more out of them.
I don't think there's a simple cookie-cutter answer. You have to do what's most effective both in the short and long term.
Short Term
In the short term, as an EA, you have to do whatever it takes to get the project moved along. Sometimes you're doing prototyping, project management, daily war rooms, bug bashes, integration work. And yes, much of it is being a great communicator and "force multiplier," getting dozens or hundreds of people on the same page.
Let's further acknowledge: That is both thankless and it eventually makes you useless. How do I know? I was that guy.
Long Term
Longer term, you need to rotate yourself back through development, whether that's a new assignment with your company, or a new gig entirely. Own something. Take it to production. Sustain it. This is how "architects" stay relevant.
Call it a "sabbatical" if you must, but do it.