To code or not to code? The software architect's dilemma
Software architects are often asked this question "So now that you are an architect you must have stopped coding, right?" As a software architect for the past 3 years I've never felt the need to give up coding completely. It's true that more of your time is devoted to understanding the customers need and translating it into both software requirements and an architecture that can be consumed by designers and developers. However, I strongly believe that coding is one skill that should never leave your arsenal and I'll explain the various instances when your coding skills will prove useful if not essential! Prototyping Many if not all complex software projects begin with some user needs that have never been implemented before. In such situations it's requisite that one or prototypes be created to determine if a feasible solution exists or not. I strongly believe that it is the duty of the Architect to take up at least a few of these prototypes, since t...