September 25, 2006
On Becoming a Software Architect: Round 2
In my previous post. I asked how many of you would be interested in hearing more tips/guidance for begining architects. Since I only got a few responses I would say the answer is "no"*. This means that apart from this post (and the previous one), I will not have posts that specifically targeting "newbie" architects (though I hope my other posts are relevant to you as well).
As a reminder, Ajay asked how do yo become an architect. Here is the reply I sent him:
I am not sure I can pin-point an exact route to becoming an architect. But maybe I can give you a few starting points. There are several pillars of what architect. There are some hard skills you can aquire: Technology depth and breadth, the ability to abstract and design.
On the soft-skills side (I blog on those here on Dr. Dobb's; see here is the first part) you can usually find courses for most of them (for example, I took courses on Strategic Planning, Negoiations and Conflict Resolution, Change Management (as in introducing change to an organization not source control), presentation skills, etc.). However, you need to practice to make the skills stick.
Another important factor is perspective--the more experience you get in various development roles the better architect you'd be. I think it is very helpful for an architect to see at least once project from inception to maintenance.
Some resources you can look at. Two good books are:
Some of the leading sites:
You might also find my architecture activities framework useful (I thought about creating a course but never got beyond syllabus outline and a couple of presentations).
A few other related sites:
Architecture Related Organizations :
Hope this helps you get started.
Arnon
* For those who did respond, you can send specific questions you have to ask@rgoarchitects.com and I'll try to help you out on my free time (or what's left of it).
Posted by Arnon Rotem-Gal-Oz at 07:42 AM Permalink
|