Add a comment

 

Re: You don't have to give up coding

I just happened to come across this post. And even though this post is a view years old I am going to comment on it because it is an omnipresent subject. I believe we shouldn't put too much focus on it. It really depends on a number of factors, not just whether or not we should or we should not (code). Personally I like coding a lot but haven't really gotten to do so in my day-time job as an Architect for a while. The reason is simple: the project is so large that my primary role is "communicator" (guiding the architects, guiding the designers, guiding the developers, guiding the client, guiding the project manager, doing estimates, and many other things). Sometimes coding can be an inhibitor as - in your specific role - more important things will not get done because you are all of the sudden operationally tied to another job (coding), deadlines, defect fixing and many other things. All I wanted to say is: it depends (on the situation you are in). Not to be able to code is not by itself a bad thing (yet). And you do not lose the respect of the developers. The bad part is that if you do not code for too long a time you are going to be too removed from reality. And this has an effect on your ability to produce architectures, designs, solutions, estimates, etc, i.e. on your abilities as an architect. So every once in a while I take on a small project where I am actually able to write code, just so I do not lose touch with my craft.

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).