One of the main reasons I have this written outlet is to provide some insight into how I’m approaching the journey towards Enterprise Architect. I’m beginning to think of the journey as transitioning between perspectives. When I design an application, I’m looking at all of the different perspectives stakeholders could approach a system from. In my history, I’ve been able to represent an end-user, data analyst, database administrator, application architect, technical support manager, infrastructure architect, change management consultant, trainer, developer, specialized application architect, and eventually enterprise architect. I’m approaching the transition to enterprise architect as adding an additional perspective. But first I must make a stop at a different position for a little bit.
How many different jobs have you had in IT? Some of the best developers and architects I’ve worked with were the best because they were able to take many things into account. They had either walked the path of the DBA, been a DBA or worked with enough DBAs to understand the key concerns of the DBA role. They had the DBA and many many more perspectives.
As an EA, I’m now looking for key perspectives I am missing to immerse myself into those roles.
Saturday, August 04, 2007
Subscribe to:
Posts (Atom)