Consider to be good designer and leader first

Simon Brown — Mon, 14 Apr 2008 13:36:49 GMT

Exactly ... the path to becoming "an architect" is an evolutionary one and, although there are a number ways of getting there, no single path is the silver bullet. This is one of the reasons why we defined the role profile - it provides suggestions for areas to focus upon while growing into the role and while undertaking it.

Consider to be good designer and leader first

Ondrej Maler — Fri, 11 Apr 2008 20:19:33 GMT

Few weeks ago I attended one workshop. The presenter was an employee of one big software company. The person is titled "architect" by his company even if his position, by my opinion, is more technology evangelist.

One of my colleagues asked him following question: "How one become an architect?". The reply was funny: "You apply for a job titled architect and they will hire you."

I think there are more roles one can play on his road to software architect. Consider technical team leader or designer. Coder/developer should start to study system design and leadership to become good designer and leader. The next step is to become an architect.

Sometimes the problem is that on small and middle sized projects single person can play all of these roles not sharing them with others. But I think there is always chance to improve your design skills while coding and to take some responsibility as a leader.

Coding the Architecture - Question of the week

Consider to be good designer and leader first

Consider to be good designer and leader first