I'm an architect myself, but I demand that I still be allowed to do some amount of coding. Sometimes it's a lot (in fact sometimes it's ALL of the coding too), sometimes it's not much at all. I demand this (and my boss agrees) because it allows me to "see the whole board" better.
When I was just doing coding, I worked with a number of architects who didn't know the first thing about front-end design. They made life much more difficult IMHO. They made design decisions in a vacumn, and ANY decision made in a vacumn tends to be a poor decision.
It's just like asking if a J2EE architect should know something about the business domain he's working in. It's certainly not the primary concern, but it's virtually never going to hurt.
Know as much as you can about as much as you can. Generalists are FAR more valuable in my experience than those that know one or two things like the back of their hand. Better to have a good grounding in a wide variety of disciples.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com
kjc wrote:
Question to all. Should a J2EE architect be an HTML expert.
Thanks in advance.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
