Is it okay for a Senior Technical Architect to know nothing about writing code?
Is it okay to not know what you're doing as a senior technical architect? In a dream I worked with someone who worked on software for a couple years and never committed anything. He lost the source so had to decompile the build and start building on that. He took code from the codebase, copied and pasted it, commented some stuff out and then checked in literally copied and pasted code with changed log statements. He didn't understand there was a problem with duplicating code like that. How does this happen? How does a senior architect get to that level and have absolutely no development experience.
6 comments
[ 2.2 ms ] story [ 22.7 ms ] threadAny management who would hire such a person would also be suspected of gross incompetence.
As you say it was only a bad dream. Hope you never have to face such a reality.
Depends on what the "senior architect" role requires.
Quite often it means making boxes and slides in large enterprisy organizations.
It is ok if they don't know everything, but would expect anyone in a senior position to know their limitations (and be able to shore them up if it's important).