It is great that you work for such a large organization that they can afford a person who attends meetings as their primary contribution. Also your organization is large enough that they can afford the technology choice mistakes you make because over time the technical environment changes dramatically and you slowly become completely out of touch and start making decisions based on what you knew first hand 5-10 years ago. I do know architects that don't code - they were super good coders and decided to become "developers of talent" instead of "developers of code". A key to this pattern of individual is that they dip back in from time to time to stay abreast of the latest technology changes. Also for someone to do the architect job well without regular coding they need to be super quick learners of new technology.
Perhaps the biggest problem is that you think you can be a good architect and avoid coding. Sounds like you are rationalizing a six-figure salary+administrative assistant just to go to meetings all day long while letting the skills that got you there fade away. "Enterprise Security Architect" = "The person who can't really protect the company but can be conveniently fired if something goes wrong". A similar argument can be made for non-technical CIOs or CSOs. Nice to have, easy to fire as a symbolic gesture when something goes wrong. No actual talent loss because all they did was sling PowerPoint at meetings. Nice work if you can get 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.
It is great that you work for such a large organization that they can afford a person who attends meetings as their primary contribution. Also your organization is large enough that they can afford the technology choice mistakes you make because over time the technical environment changes dramatically and you slowly become completely out of touch and start making decisions based on what you knew first hand 5-10 years ago. I do know architects that don't code - they were super good coders and decided to become "developers of talent" instead of "developers of code". A key to this pattern of individual is that they dip back in from time to time to stay abreast of the latest technology changes. Also for someone to do the architect job well without regular coding they need to be super quick learners of new technology.
Perhaps the biggest problem is that you think you can be a good architect and avoid coding. Sounds like you are rationalizing a six-figure salary+administrative assistant just to go to meetings all day long while letting the skills that got you there fade away. "Enterprise Security Architect" = "The person who can't really protect the company but can be conveniently fired if something goes wrong". A similar argument can be made for non-technical CIOs or CSOs. Nice to have, easy to fire as a symbolic gesture when something goes wrong. No actual talent loss because all they did was sling PowerPoint at meetings. Nice work if you can get it.