what does it take to be a Software Architect?

[Rainier Buccat]

Sorry for the lame question ^^;; I know this term have several definitions all over the net. However I think I cannot convince myself unless I get raw responses from people XD

Thanks !! ^^


     

[Randell Benavidez]

Follow this thread:
http://tech.dir.groups.yahoo.com/group/pinoyjug/message/19348 *What does it
mean to be an architect? (was: Write Dumb Code)*

[Alistair Israel]

On Tue, Sep 29, 2009 at 3:10 PM, Rainier Buccat <darkblue778@...> wrote:
>
> Sorry for the lame question ^^;; I know this term have several definitions all over the net. However I
> think I cannot convince myself unless I get raw responses from people XD

I go by the "Role of the Software Architect" on:
http://www.wwisa.org/wwisamain/role.htm

- a

[joen]

Here's a good paper written by Martin Fowler.

http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf

I like how he explains software architecture, and the software architect's
role. I just wish more companies who do software look at it this way.

Joen Moreno

On Tue, Sep 29, 2009 at 2:10 AM, Rainier Buccat <darkblue778@...>wrote:

>
>
> Sorry for the lame question ^^;; I know this term have several definitions
> all over the net. However I think I cannot convince myself unless I get raw
> responses from people XD
>
> Thanks !! ^^
>
>  
>

[Jay Dominic Sto. Tomas]

Well, in my point of view, being a software "architect" is not for someone
who just got out of college no matter how high their grades are.  Regardless
if you turn out to be a generalist or a specialist software architect, you
need to have spent a significant amount of time (and i'm talking years here)
doing actual projects, coding, reading and applying best practices,
tinkering and experimenting with software they choose or are required to
work with.  More importantly, that person has to have a good deal of
experience in FAILING (not just succeeding).  That's how you know about what
works and what doesn't.  There's a ton of other stuff I could say that could
be considered as requirements for being a software architect.

Btw, I just want to make it crystal clear that software "architect" does not
equal software "engineer" or "developer"...  I remember talking to some
youngsters fresh out of a computer college who thought that they were
already software architects just because they were working on a relatively
small project where they designed and coded the entire system... :)

Anyway, I'm pretty sure a lot of other people here have quite a bit of juicy
stuff to add to what I just said here...  :)

Regards,

Jay


On Tue, Sep 29, 2009 at 3:10 PM, Rainier Buccat <darkblue778@...>wrote:

>
>
> Sorry for the lame question ^^;; I know this term have several definitions
> all over the net. However I think I cannot convince myself unless I get raw
> responses from people XD
>
> Thanks !! ^^
>
>  
>

[JonT-3]

Agree ako dyan pareng Jay ...

--- In pinoyjug@..., Jay Dominic <jaydominic@...> wrote:

>
> Well, in my point of view, being a software "architect" is not for someone
> who just got out of college no matter how high their grades are.  Regardless
> if you turn out to be a generalist or a specialist software architect, you
> need to have spent a significant amount of time (and i'm talking years here)
> doing actual projects, coding, reading and applying best practices,
> tinkering and experimenting with software they choose or are required to
> work with.  More importantly, that person has to have a good deal of
> experience in FAILING (not just succeeding).  That's how you know about what
> works and what doesn't.  There's a ton of other stuff I could say that could
> be considered as requirements for being a software architect.
>
> Btw, I just want to make it crystal clear that software "architect" does not
> equal software "engineer" or "developer"...  I remember talking to some
> youngsters fresh out of a computer college who thought that they were
> already software architects just because they were working on a relatively
> small project where they designed and coded the entire system... :)
>
> Anyway, I'm pretty sure a lot of other people here have quite a bit of juicy
> stuff to add to what I just said here...  :)
>
> Regards,
>
> Jay
>
>
> On Tue, Sep 29, 2009 at 3:10 PM, Rainier Buccat <darkblue778@...>wrote:
>
> >
> >
> > Sorry for the lame question ^^;; I know this term have several definitions
> > all over the net. However I think I cannot convince myself unless I get raw
> > responses from people XD
> >
> > Thanks !! ^^
> >
> >  
> >
>