Agree. It is unfashionable, but in the long run, having a unified technical vision for your product breaks down silos and makes products easy to maintain.
Here's the problems I've had with this position:
1) Not innovating. Basically you decided 10 years ago to use Java 1.4.2 and by golly it was good enough then it's good enough now. You have to rock the boat occasionally. And yes, your applications should require a rewrite every 3-5 years.
2) I've worked with too many people that were promoted into the role by time at the job, instead of skill, which is the real anti-pattern.
3) They "don't code." This is ridiculous. Eat your own dog food. If you can't code faster/better than the engineers underneath you, you need to be replaced.
Here's the problems I've had with this position:
1) Not innovating. Basically you decided 10 years ago to use Java 1.4.2 and by golly it was good enough then it's good enough now. You have to rock the boat occasionally. And yes, your applications should require a rewrite every 3-5 years.
2) I've worked with too many people that were promoted into the role by time at the job, instead of skill, which is the real anti-pattern.
3) They "don't code." This is ridiculous. Eat your own dog food. If you can't code faster/better than the engineers underneath you, you need to be replaced.