"Enterprise Security Architect" might be perfectly fine without writing any code.
Software architect should code because software architecture mostly expressed in code, somewhat in diagrams but never in Word or PowerPoint.
PowerPoint software architecture is dead at the moment it is created. Software architecture evolves with software, it is a progressive development in time and is never fixed. Only by keeping up with the product itself, how it is written, modularised, what tools, libraries and frameworks are used, what infrastructure components are good now and will probably not be as good in a month time - all this evolves continuously together with code.
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.
"Enterprise Security Architect" might be perfectly fine without writing any code.
Software architect should code because software architecture mostly expressed in code, somewhat in diagrams but never in Word or PowerPoint.
PowerPoint software architecture is dead at the moment it is created. Software architecture evolves with software, it is a progressive development in time and is never fixed. Only by keeping up with the product itself, how it is written, modularised, what tools, libraries and frameworks are used, what infrastructure components are good now and will probably not be as good in a month time - all this evolves continuously together with code.