Add a comment

 

Re: You don't have to give up coding

I think the #1 downside to being a non-coding architect is you will very quickly lose the respect of the developers. I've touched on that topic briefly in a blog article I wrote on becoming an architect. Also when push comes to shove it helps to be able to dive in, fix bugs and really get your hands dirty. I think the architect role can be so hard sometimes, that I think about "dropping back" to just being a principal software engineer. Architects often have too many expectations - part architect, part developer, part project manager, part strategist etc.

Re: You don't have to give up coding


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).