Not merely architecting

Monday, July 24. 2006

I've been looking for more information about the skill set required to characterize a software architect since I read my ex-colleague's post on that topic, to see if I'm already qualified to be in the position. In short, the position is definitely not as simple as the title tells, which is architecting software. It literally requires technical, leadership and even project management skills. Of course, everyone has different definition and I've heard there's software architect doing business consulting and pre-sales stuffs.

Posted by Steven Yong in non-computer at 08:39 | Comment (1) | Trackbacks (0)

...

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

Thanks for reading my post!

I wrote that based on a little rant I had about another ex-colleague who absolutely didn't understand what a Software Architect was. She said that a Software Architect was someone who knew a lot about hardware besides software. That got me a bit annoyed.

Yea, unfortunately, some architects are required to do pre-sales and that happens in certain organizations because some organizations have a set of products/methodology that the wish to "sell" to the customer.

I thought of writing another article on the difficulties becoming a Java Software Architect but then, I think I'll focus on more generic issues. It is unfortuate these days that the Software Architect needs to keep up to date with what "frameworks" and methodologies out there now.

I feel that in order to make the leap of faith into Software Architecture, one should understand software AND hardware carefully as well as play roles in the SDLC (except for pure project management) in order to understand how to architect something based on all requirements (business, software, hardware, project, resources...).

So, are you ready to take that leap of faith?