Oct
14
Posted by:
Joe Brinkman
10/14/2005 7:00 AM
This is part of a series of blogs I will be doing on software development and how that applies to DotNetNuke development. As one of the Architects on the DotNetNuke team I try to keep a focus on the big picture. How does everything fit together? What is the impact of making a change to this part of the platform infrastructure?
How many times have we seen developers sporting the titles: Software Developer, Software Engineer, Computer Scientist and my favorite Software Architect? We have all seen it at some point in our careers. We get the promotion that comes with a new title, new business cards and the same old pay. In many cases we are doing exactly the same job as we were when we had the old title. At one point in time, these titles all had meaning. Each was separate and distinct from the other. Over the last 20 years title inflation has blurred the lines between a senior developer, an engineer and an architect.
I ran across a recent set of articles on Artima Developer in which the role of the software architect is discussed. These articles provided me with some fresh insight on the role of the Software Architect and his/her importance to the software development process. The six part series:
is a set of discussions which really help describe the many roles of the Architect in software development. Read through the articles and in my next installment we can discuss how this relates to software development on DotNetNuke. How does our process mesh up with those discussed by Bill Venners and Luke Hohmann, and ways that things might be slightly different in the OS arena.